-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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: LEAP-1356: Add custom button props #6787
base: develop
Are you sure you want to change the base?
Conversation
… to table row Added support for custom button props in buttons and included a `data-leave` attribute in table rows for unsaved changes checks triggers.
✅ Deploy Preview for label-studio-docs-new-theme canceled.
|
✅ Deploy Preview for heartex-docs canceled.
|
/git merge develop
|
…1356/unsaved-sidebar # Conflicts: # web/libs/datamanager/src/components/Common/Table/TableRow/TableRow.jsx
697a0d9
to
1be06b9
Compare
Ensure the `data-leave` attribute is added to relevant components to manage navigation actions properly. This change supports identifying actions that trigger a leave event.
/git merge develop
|
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 over all - approved but would love to see some unit tests to check if the data-leave attribute is being added as expected
/git merge develop
|
Follow Merge downstream workflow has been failed. |
Added support for custom button props in buttons and included a
data-leave
attribute in table rows for unsaved changes checks triggers.PR fulfills these requirements
[fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made
ex.fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
Change has impacts in these area(s)
(check all that apply)
Describe the reason for change
(link to issue, supportive screenshots etc.)
What does this fix?
(if this is a bug fix)
What is the new behavior?
(if this is a breaking or feature change)
What is the current behavior?
(if this is a breaking or feature change)
What libraries were added/updated?
(list all with version changes)
Does this change affect performance?
(if so describe the impacts positive or negative)
Does this change affect security?
(if so describe the impacts positive or negative)
What alternative approaches were there?
(briefly list any if applicable)
What feature flags were used to cover this change?
(briefly list any if applicable)
Does this PR introduce a breaking change?
(check only one)
What level of testing was included in the change?
(check all that apply)
Which logical domain(s) does this change affect?
(for bug fixes/features, be as precise as possible. ex. Authentication, Annotation History, Review Stream etc.)