-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feat/doc sign #17
Feat/doc sign #17
Conversation
jesusantguerrero
commented
Jun 30, 2020
•
edited
Loading
edited
- Add support for fixed filters in gw-browse
- Add support for date range
- Add top left pagination slots
- Add actions slot
@@ -370,13 +377,19 @@ export default { | |||
}, | |||
searchableFields() { | |||
return this.tableFields.filter(field => field.searchable).map(field => field.name); | |||
}, | |||
mainDateField() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So what happens where there is more than one date field in the filterable fields?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It should't be more than one by the moment that's why is called mainDateField; but later, maybe we can allow the User decide which date field
to use or address the problem in custom filters.
what do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Later is okay.
Co-authored-by: Rogelio Morey <rogelio@mctekk.com>