mirror of
https://github.com/woodpecker-ci/woodpecker.git
synced 2024-06-10 17:39:37 +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> ![image](https://github.com/woodpecker-ci/woodpecker/assets/3391958/a254f1e0-ce17-43a9-9e8b-72252296fd6f) 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. ![image](https://github.com/woodpecker-ci/woodpecker/assets/3391958/7bf751e1-f2a6-481c-bee7-a27d27cf8adb) ![image](https://github.com/woodpecker-ci/woodpecker/assets/3391958/e5673dc7-81c1-4fd4-bef9-14494bc5aa27) 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>
91 lines
2.2 KiB
Vue
91 lines
2.2 KiB
Vue
<template>
|
|
<div v-for="option in options" :key="option.value" class="flex items-center mb-2">
|
|
<input
|
|
:id="`radio-${id}-${option.value}`"
|
|
type="radio"
|
|
class="radio relative flex-shrink-0 border bg-wp-control-neutral-100 border-wp-control-neutral-200 cursor-pointer rounded-full w-5 h-5 checked:bg-wp-control-ok-200 checked:border-wp-control-ok-200 focus-visible:border-wp-control-neutral-300 checked:focus-visible:border-wp-control-ok-300"
|
|
:value="option.value"
|
|
:checked="innerValue.includes(option.value)"
|
|
@click="innerValue = option.value"
|
|
/>
|
|
<div class="flex flex-col ml-4">
|
|
<label class="cursor-pointer text-wp-text-100" :for="`radio-${id}-${option.value}`">{{ option.text }}</label>
|
|
<span v-if="option.description" class="text-sm text-wp-text-alt-100">{{ option.description }}</span>
|
|
</div>
|
|
</div>
|
|
</template>
|
|
|
|
<script lang="ts">
|
|
import { computed, defineComponent, PropType, toRef } from 'vue';
|
|
|
|
import { RadioOption } from './form.types';
|
|
|
|
export default defineComponent({
|
|
name: 'RadioField',
|
|
|
|
components: {},
|
|
|
|
props: {
|
|
modelValue: {
|
|
type: String,
|
|
required: true,
|
|
},
|
|
|
|
options: {
|
|
type: Array as PropType<RadioOption[]>,
|
|
required: true,
|
|
},
|
|
},
|
|
|
|
emits: {
|
|
// eslint-disable-next-line @typescript-eslint/no-unused-vars
|
|
'update:modelValue': (_value: RadioOption['value']): boolean => true,
|
|
},
|
|
|
|
setup: (props, ctx) => {
|
|
const modelValue = toRef(props, 'modelValue');
|
|
const innerValue = computed({
|
|
get: () => modelValue.value,
|
|
set: (value) => {
|
|
ctx.emit('update:modelValue', value);
|
|
},
|
|
});
|
|
|
|
const id = (Math.random() + 1).toString(36).substring(7);
|
|
|
|
return {
|
|
id,
|
|
innerValue,
|
|
};
|
|
},
|
|
});
|
|
</script>
|
|
|
|
<style scoped>
|
|
.radio {
|
|
appearance: none;
|
|
outline: 0;
|
|
cursor: pointer;
|
|
transition: background 175ms cubic-bezier(0.1, 0.1, 0.25, 1);
|
|
}
|
|
|
|
.radio::before {
|
|
position: absolute;
|
|
content: '';
|
|
display: block;
|
|
top: 50%;
|
|
left: 50%;
|
|
width: 7px;
|
|
height: 7px;
|
|
border-radius: 50%;
|
|
background: white;
|
|
transform: translate(-50%, -50%);
|
|
opacity: 0;
|
|
@apply dark:bg-white;
|
|
}
|
|
|
|
.radio:checked::before {
|
|
opacity: 1;
|
|
}
|
|
</style>
|