Skip to content
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: Unify record-level actions for all tasks (Validate, Clear, and Discard) #2280

Merged

Conversation

leiyre
Copy link
Member

@leiyre leiyre commented Feb 2, 2023

Description

This PR aligns record-level actions for all tasks (Validate, Clear, and Discard) and include the new design

Closes #2266
See #2264

Type of change

(Please delete options that are not relevant. Remember to title the PR according to the type of change)

  • New feature (non-breaking change which adds functionality)

How Has This Been Tested

(Please describe the tests that you ran to verify your changes. And ideally, reference tests)

  • test for RecordActionButtons
  • update snapshot

Checklist

  • I have merged the original branch into my forked branch
  • follows the style guidelines of this project
  • I did a self-review of my code
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works

!annotationEnabled
? 'content--exploration-mode'
: 'content--annotation-mode',
]"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

separate the binded classes and the other classes =>
class="content content--separator" :class="[ !annotationEnabled ? 'content--exploration-mode' : 'content--annotation-mode', ]"

let newS = {
score: 1,
text: sentence,
text: this.record.sentenceForAnnotation,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is sentenceForAnnotation always a properties of record ? if not, manage the undefined case

});
it("expect to show discard button active", async () => {
testIfButtonIsDisabled("discard", undefined);
});
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why undefined and not null ?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The response if is not disabled is "undefined" because disabled is undefined in the wrapper attributes

@leiyre leiyre merged commit 0711540 into feature/bulk-annotation-improvement Feb 3, 2023
@leiyre leiyre deleted the feat/unify_record_level_actions branch February 3, 2023 08:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants