-
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
654 gs lineage filter add button to delete current input #662
654 gs lineage filter add button to delete current input #662
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This is a preview of the changelog of the next release. If this branch is not up-to-date with the current main branch, the changelog may not be accurate. Rebase your branch on the main branch to get the most accurate changelog. Note that this might contain changes that are on main, but not yet released. Changelog: 0.13.0 (2025-01-21)⚠ BREAKING CHANGES
Features
Code Refactoring |
components/src/preact/lineageFilter/LineageFilterChangedEvent.ts
Outdated
Show resolved
Hide resolved
3aefe97
to
70cb363
Compare
00a9074
to
f3a57f5
Compare
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.
looks good to me and when I tested the preview it also looks ok - just one naming question/ suggestion
Just a little commit message nitpick: I usually prefer to have the exact component tag in the message. "lineage filter" seems a little too unspecific to me. That's why I usually write messages that target a single component in the style |
95bc4e6
to
469f475
Compare
BREAKING CHANGE: Rename initialValue to value for gs-lineage-filter
469f475
to
b22b710
Compare
resolves #654
Summary
Downshift is now used for the lineage filter.
Breaking change: renames initialValue to value to be in line with the generic input element.
Screenshot
The input with delete button
PR Checklist