-
Notifications
You must be signed in to change notification settings - Fork 4.1k
TRUNK-5911: Migrate ConceptStopWord to JPA annotations #5378
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
base: master
Are you sure you want to change the base?
Conversation
|
@pidsonn here we go with the next build failure. |
|
Hi @dkayiwa, Could you please approve the workflows? |
Done. |
| assertNull(orderGroupAttributeType.getRetireReason()); | ||
| } | ||
|
|
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.
Can we discard all these formatting changes?
| <mapping class="org.openmrs.ConceptReferenceRange"/> | ||
| </session-factory> | ||
|
|
||
| <!-- Mapping for ConceptStopWord domain switched to annotations --> |
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.
What is this for?
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.
It was optional having it.
I have removed it.
| private Integer conceptStopWordId; | ||
|
|
||
|
|
||
| @Column(name = "word", nullable = false) |
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.
Did you intentionally leave out the length?
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.
No, that was an oversight. I’ve updated the commit to include the length.
Description of what I changed
Issue I worked on
see https://issues.openmrs.org/browse/TRUNK-5911
Checklist: I completed these to help reviewers :)
[x ] My IDE is configured to follow the code style of this project.
No? Unsure? -> configure your IDE, format the code and add the changes with
git add . && git commit --amendI have added tests to cover my changes. (If you refactored
existing code that was well tested you do not have to add tests)
No? -> write tests and add them to this commit
git add . && git commit --amend[x ] I ran
mvn clean packageright before creating this pull request andadded all formatting changes to my commit.
No? -> execute above command
[ x] All new and existing tests passed.
No? -> figure out why and add the fix to your commit. It is your responsibility to make sure your code works.
[x ] My pull request is based on the latest changes of the master branch.
No? Unsure? -> execute command
git pull --rebase upstream master