rattail/tailbone
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

More data type fixes for <tailbone-datepicker>

Browse source 
traditionally the caller has always dealt with string values only, so
the component should never emit events with date values, etc.
This commit is contained in:
Lance Edgar 2024-05-07 18:20:26 -05:00
parent d607ab2981
commit 28fb3f44a7
1 changed files with 9 additions and 12 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
tailbone/static/js/tailbone.buefy.datepicker.js
View file

@ -27,20 +27,14 @@ const TailboneDatepicker = {
},
data() {
let buefyValue = this.value
if (buefyValue && !buefyValue.getDate) {
buefyValue = this.parseDate(this.value)
}
return {
buefyValue,
buefyValue: this.parseDate(this.value),
}
},
watch: {
value(to, from) {
if (this.buefyValue != to) {
this.buefyValue = to
}
this.buefyValue = this.parseDate(to)
},
},
@ -61,13 +55,16 @@ const TailboneDatepicker = {
},
parseDate(date) {
if (typeof(date) == 'string') {
// note, this assumes classic YYYY-MM-DD (i.e. ISO?) format
var parts = date.split('-')
return new Date(parts[0], parseInt(parts[1]) - 1, parts[2])
}
return date
},
dateChanged(date) {
this.$emit('input', date)
this.$emit('input', this.formatDate(date))
},
focus() {