-
Notifications
You must be signed in to change notification settings - Fork 1
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: Apps-3035 create filters drop down component #664
Conversation
Percy ScreenshotsIn order to conserve our percy screenshot allowance, percy is not configured to run automatically. Please make sure the PR is ready and all other checks are passing, then start it manually:
|
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.
Nice! 👍🏾
# [3.42.0](v3.41.0...v3.42.0) (2024-12-13) ### Features * Apps-3035 create filters drop down component ([#664](#664)) ([8dbad4a](8dbad4a))
🎉 This PR is included in version 3.42.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Connected to APPS-3035
Component Created: FiltersDropdown.vue based on this component request
Stories: ~/stories/FiltersDropdown.stories.js
Spec: ~/stories/FiltersDropdown.spec.js
Notes:
This PR adds the FiltersDropdown.vue component to the component library, along with its styles, test, and story files.
This component currently uses v-model which cuts down on script needed.
Because a child's v-model data is always in sync with the parent's model variable, I did not include emits yet despite them being mentioned in the requirements, as I don't believe they will do anything. However, if we need the parent data to be in a different state than the v-model data, we can use the pattern of assigning an initial data prop to a data ref and then emitting to the parent when we want it to update the data. This is somewhat what
dateFilter.vue
does.Checklist:
library-website-nuxt dev server