From dda790b5c4891d1e1aae1b8a6748c879ba672f70 Mon Sep 17 00:00:00 2001
From: Lance Edgar <ledgar@techsupport.coop>
Date: Thu, 23 May 2019 13:57:44 -0500
Subject: [PATCH] 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
---
 tailbone/static/js/tailbone.buefy.datepicker.js | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/tailbone/static/js/tailbone.buefy.datepicker.js b/tailbone/static/js/tailbone.buefy.datepicker.js
index 52018a3e..52f01937 100644
--- a/tailbone/static/js/tailbone.buefy.datepicker.js
+++ b/tailbone/static/js/tailbone.buefy.datepicker.js
@@ -11,6 +11,7 @@ const TailboneDatepicker = {
         'icon="calendar-alt"',
         ':date-formatter="formatDate"',
         ':date-parser="parseDate"',
+        ':value="value ? parseDate(value) : null"',
         '@input="dateChanged"',
         '>',
         '</b-datepicker>'
@@ -19,6 +20,7 @@ const TailboneDatepicker = {
     props: {
         name: String,
         id: String,
+        value: String
     },
 
     methods: {