This commit is contained in:
2019-11-29 19:26:30 +00:00
parent 852cf50084
commit 86f2a7d5e3
3 changed files with 17 additions and 3 deletions

View File

@@ -50,6 +50,10 @@ TODO: Tag control
- kind of weird if you type a search letter it sticks when you make a selection as a partial new entry - kind of weird if you type a search letter it sticks when you make a selection as a partial new entry
- drop down should search immediately or bring up something? Or say type to search?? - drop down should search immediately or bring up something? Or say type to search??
- Test it out completely, there seems to be some minor strangeness. - Test it out completely, there seems to be some minor strangeness.
- DO: if type a letter then make a selection from list, typing should clear, that appears to be the only issue with it
- DO: it would be good UI if it prompted user to type to search
- DO: can select empty item in list, shouldn't do anything if click on that
- DO: Need LT key: TYPETOSEARCHPROMPT - "Start typing to search..." and NO_SEARCH_RESULTS - "No results" ( no-data-text="No results" placeholder="Start typing to Search")
TODO: Form customization - hidden fields support TODO: Form customization - hidden fields support

View File

@@ -71,6 +71,7 @@ export default {
"WikiPage", "WikiPage",
"Duplicate", "Duplicate",
"RecordHistory", "RecordHistory",
"Search",
"ErrorFieldLengthExceeded", "ErrorFieldLengthExceeded",
"ErrorStartDateAfterEndDate", "ErrorStartDateAfterEndDate",
"ErrorRequiredFieldEmpty", "ErrorRequiredFieldEmpty",

View File

@@ -8,14 +8,22 @@
v-on:input="$emit('input', $event)" v-on:input="$emit('input', $event)"
:items="sourcetags" :items="sourcetags"
:loading="tagSearchUnderway" :loading="tagSearchUnderway"
:placeholder="lt('Search')"
:search-input.sync="tagSearchEntry" :search-input.sync="tagSearchEntry"
hide-selected hide-selected
multiple multiple
chips chips
clearable
deletable-chips deletable-chips
cache-items cache-items
> >
<!-- <template v-slot:no-data>
<v-list-item>
<v-list-item-title>
Search for your favorite
<strong>TAG</strong>
</v-list-item-title>
</v-list-item>
</template> -->
<template slot="no-data" v-if="tagSearchEntry"> <template slot="no-data" v-if="tagSearchEntry">
<v-container> <v-container>
<v-row row> <v-row row>
@@ -35,7 +43,7 @@
</template> </template>
<script> <script>
///////////////////////////////////////////////////////////////////////////////////////////////////////////// /////////////////////////////////////////////////////////////////////////////////////////////////////////////
/* Xeslint-disable */ /* eslint-disable */
//////////////////////////////////////////////////////////////////////////////////////////////////////////// ////////////////////////////////////////////////////////////////////////////////////////////////////////////
export default { export default {
@@ -49,7 +57,7 @@ export default {
data() { data() {
return { return {
sourcetags: [""], sourcetags: [],
tagSearchEntry: null, tagSearchEntry: null,
tagSearchUnderway: false, tagSearchUnderway: false,
initialized: false initialized: false
@@ -84,6 +92,7 @@ export default {
value(val) { value(val) {
//this ensures the parent form gets the onchange event //this ensures the parent form gets the onchange event
//not actually sure why there are two here but it worked with the datetime picker so I replicated it here //not actually sure why there are two here but it worked with the datetime picker so I replicated it here
//To answer above it appears both are necessary for proper operation
this.$emit("input", val); this.$emit("input", val);
this.$emit("change", val); this.$emit("change", val);
} }