-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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: 5495: Add a note to a relation #5995
base: develop
Are you sure you want to change the base?
Conversation
👷 Deploy request for label-studio-docs-new-theme pending review.Visit the deploys page to approve it
|
👷 Deploy request for heartex-docs pending review.Visit the deploys page to approve it
|
Hi @Car85, if you want to be eligible for the bounty of $50 you'll need to apply to the issue here: |
Hi @robinclaes , it seems that some steps are not included. Once they are completed, I will send the solution. |
I'm on the tests right now, will get to the PR soon. |
This PR is stale because it has been open 45 days with no activity. Remove |
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
#5495
What does this fix?
What is the new behavior?
Users can add a note to each relation.
What is the current behavior?
Users can't add a note to each relation.
What libraries were added/updated?
DOMPurify
Does this change affect performance?
Now users can avoid confusion in the relations by adding notes.
Does this change affect security?
DOMPurify avoid malicious code in the TextArea
What alternative approaches were there?
What feature flags were used to cover this change?
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?
Relations