mirror of
https://github.com/woodpecker-ci/woodpecker.git
synced 2024-06-02 12:50:30 +00:00
dca01e6817
Fixes: https://github.com/woodpecker-ci/woodpecker/issues/1079 What do you think about using a consistent `woodpecker` color scheme? Right now, the `lime` color scheme from windicss is used that does not really fit the primary color used for the documentation website. I have used the primary color `#4CAF50` from the docs and created a color palette with https://palettte.app/: <details> <summary>JSON source</summary> ```Json [ { "paletteName": "New Palette", "swatches": [ { "name": "New Swatch", "color": "166E30" }, { "name": "New Swatch", "color": "248438" }, { "name": "New Swatch", "color": "369943" }, { "name": "New Swatch", "color": "4CAF50" }, { "name": "New Swatch", "color": "68C464" }, { "name": "New Swatch", "color": "8AD97F" } ] } ] ``` </details>  I have added this color scheme to the windicss config and replaced the use of `lime` in the UI. While `woodpecker-300` would be the primary color that is used for the docs, I currently use `woodpecke-400` as primary color for the UI to fix some contrast issues.   What do you think? If you would like to stay with the current colors, that's fine for me, I can just use the custom CSS feature in this case. --------- Co-authored-by: 6543 <6543@obermui.de>
67 lines
1.7 KiB
Vue
67 lines
1.7 KiB
Vue
<template>
|
|
<div class="space-y-4 text-wp-text-100">
|
|
<ListItem
|
|
v-for="secret in secrets"
|
|
:key="secret.id"
|
|
class="items-center !bg-wp-background-200 !dark:bg-wp-background-100"
|
|
>
|
|
<span>{{ secret.name }}</span>
|
|
<div class="ml-auto space-x-2">
|
|
<Badge v-for="event in secret.event" :key="event" :label="event" />
|
|
</div>
|
|
<IconButton
|
|
icon="edit"
|
|
class="ml-2 w-8 h-8"
|
|
:title="$t('repo.settings.secrets.edit')"
|
|
@click="editSecret(secret)"
|
|
/>
|
|
<IconButton
|
|
icon="trash"
|
|
class="ml-2 w-8 h-8 hover:text-wp-control-error-100"
|
|
:is-loading="isDeleting"
|
|
:title="$t('repo.settings.secrets.delete')"
|
|
@click="deleteSecret(secret)"
|
|
/>
|
|
</ListItem>
|
|
|
|
<div v-if="secrets?.length === 0" class="ml-2">{{ $t(i18nPrefix + 'none') }}</div>
|
|
</div>
|
|
</template>
|
|
|
|
<script lang="ts" setup>
|
|
import { toRef } from 'vue';
|
|
import { useI18n } from 'vue-i18n';
|
|
|
|
import IconButton from '~/components/atomic/IconButton.vue';
|
|
import ListItem from '~/components/atomic/ListItem.vue';
|
|
import { Secret } from '~/lib/api/types';
|
|
|
|
const props = defineProps<{
|
|
modelValue: Secret[];
|
|
isDeleting: boolean;
|
|
i18nPrefix: string;
|
|
}>();
|
|
|
|
const emit = defineEmits<{
|
|
(event: 'edit', secret: Secret): void;
|
|
(event: 'delete', secret: Secret): void;
|
|
}>();
|
|
|
|
const i18n = useI18n();
|
|
|
|
const secrets = toRef(props, 'modelValue');
|
|
|
|
function editSecret(secret: Secret) {
|
|
emit('edit', secret);
|
|
}
|
|
|
|
function deleteSecret(secret: Secret) {
|
|
// TODO use proper dialog
|
|
// eslint-disable-next-line no-alert, no-restricted-globals
|
|
if (!confirm(i18n.t('repo.settings.secrets.delete_confirm'))) {
|
|
return;
|
|
}
|
|
emit('delete', secret);
|
|
}
|
|
</script>
|