Flo Edelmann comments

Results 458 comments of


                                            Flo Edelmann

Make eslint-compact matcher compatible with Stylelint

@bryanmacfarlane Done :ok_hand:

Allow disabling country restrictions

> Some restrictions do exist because SC(EE) tagging is not wanted by community Okay, so options 1, 3 and 5 are ruled out. But would implementing this specifically for the...

Crossing marking extension not visible

Or split up the quest into the regular, unmodified "Does this crossing have markings on the ground?" quest, and a separate SCEE-specific "What markings are on the ground here?" quest...

Add a `Legend`

I know it's not exactly what you asked for, but there is a community-maintained color legend in the OSM wiki: https://wiki.openstreetmap.org/wiki/StreetComplete/Overlays

Rule `vue/v-on-handler-style` default auto fix will bring breaking change into code

I guess changing the fix to a suggestion that has to be manually applied makes sense here. PRs welcome for that!

vue/no-unused-properties -- reports properties of type 'never' as unused.

I guess that could be a small improvement (if the types are known because typescript-eslint's parser is used). PR welcome for that!

vue/require-explicit-emits - defineModel not supported

Is this the recommended usage? I'd rather do this with `defineModel`: ```vue const modelValue = defineModel(); ```

vue/require-explicit-emits - defineModel not supported

@corentind59 See my comment above; you could rewrite this as follows: ```vue const visible = defineModel('visible') const emit = defineEmits() const name = ref('') function handleSubmit() { emit('submit', name.value) }...

Normalize CLI options, switch to yargs

Also bring all CLI tools' help messages into line. If they output usable plugin keys, those should not be hardcoded, but taken from `plugins.json`.

Normalize CLI options, switch to yargs

Also update references to the CLI tool usage in the docs and in GitHub tests.