Fix datepicker behavior for grid filters
apparently we *do* need to accept a 'value' prop for tailbone-datepicker, to round out the v-model support
This commit is contained in:
parent
b829cd260c
commit
dda790b5c4
|
@ -11,6 +11,7 @@ const TailboneDatepicker = {
|
||||||
'icon="calendar-alt"',
|
'icon="calendar-alt"',
|
||||||
':date-formatter="formatDate"',
|
':date-formatter="formatDate"',
|
||||||
':date-parser="parseDate"',
|
':date-parser="parseDate"',
|
||||||
|
':value="value ? parseDate(value) : null"',
|
||||||
'@input="dateChanged"',
|
'@input="dateChanged"',
|
||||||
'>',
|
'>',
|
||||||
'</b-datepicker>'
|
'</b-datepicker>'
|
||||||
|
@ -19,6 +20,7 @@ const TailboneDatepicker = {
|
||||||
props: {
|
props: {
|
||||||
name: String,
|
name: String,
|
||||||
id: String,
|
id: String,
|
||||||
|
value: String
|
||||||
},
|
},
|
||||||
|
|
||||||
methods: {
|
methods: {
|
||||||
|
|
Loading…
Reference in a new issue