Nico Hoffmann ෴.
Nico Hoffmann ෴.
Stricter code coverage annotations + added some more tests
## This PR … Tried to fix #5126 - while the issue itself remains without a good solution, some improvements to the methods structure and performance could be made. Added...
## Status ### Todo - [ ] Add native validity alongside vuelidate as much as possible - [ ] https://github.com/getkirby/kirby/pull/6253 - [ ] https://github.com/getkirby/kirby/pull/6254 - [ ] Add lab examples...
``` [Vue warn]: Invalid prop: type check failed for prop "value". Expected Boolean, got String with value "true". found in ---> at /Users/nhoffmann/Sites/kirby/sites/sandbox/kirby/panel/src/components/Forms/Input/ToggleInput.vue at /Users/nhoffmann/Sites/kirby/sites/sandbox/kirby/panel/src/components/Forms/Previews/ToggleFieldPreview.vue ```
Guess they could've been one method but I missed `A::join()` before
I think it would be good to write down an overview of Panel events (global emit) and see where we have inconsistencies, gaps... Fill them, align them and then document...
To be considered/though through: It could be more convenient to have a fallback/default for `current` if no specific one is defined by a custom menu entry. The default could be...
When using e.g. tags field with options from API for autocomplete it should be possible to pass the current query value to the API