-
Notifications
You must be signed in to change notification settings - Fork 438
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
Process mention on annotation creation #9322
Conversation
cc37bf2
to
6dfab59
Compare
be88a11
to
7980259
Compare
7980259
to
008f84f
Compare
008f84f
to
42922ed
Compare
Not entirely sure if I need to add view / functional tests |
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 in general. My main feedback is that we should probably run the mentions-specific logic only if the at_mentions
feature is enabled.
42922ed
to
510fc62
Compare
510fc62
to
5ce9754
Compare
5ce9754
to
85f0de1
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 👍
I might have split this into two PRs, one for processing the mentions and another one to expose them the API (addressing the latest changes there).
But this PR comes after the PoC one so we are already familiar with the changes anyway. The API field name change can be addressed in a follow up PR as you say 👍
85f0de1
to
13181bc
Compare
13181bc
to
06563e6
Compare
06563e6
to
dd7d8ee
Compare
Refs #9304
See testing instructions in the PoC #9279
Most everything has been addressed in the PoC