-
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
[UILISTS-91] Create typings for ui-lists components usage #47
Conversation
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
* value and displayed on the page), or an object enabling more customization. | ||
*/ | ||
export type FilterGroupsConfigValue = | ||
| string |
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.
This is a new syntax thing for me... Does the leading |
just get ignored or does it have some semantics beyond just making the formatting look nice?
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.
Yep, the leading one gets ignored specifically to make things like this line up pretty
/** @deprecated use dismissible instead */ | ||
dismissable?: true; |
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
Jira UILISTS-91
There is improper usage of
FilterGroups
andConfirmationModal
inui-lists
which will break if this is merged. These issues should be fixed inui-lists
and merged with/before. See UILISTS-95Adds
any
and marked@deprecated
rg LegacyPopover ./node_modules/@folio/*
shows that this component is not used anymore. Maybe we should remove it entirely?stripes-components
itself...Improves
buttonStyle
typings for easier reusePopper
propsPopper
propsPopper
propsPopper
propsBonus PRs made as part of this