TRUNK-5950: Part 2 - Implement name column autofill logic #5653
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This is Part 2 of the TRUNK-5950 work (Part 1 was merged recently).
This PR adds the logic to automatically populate the mandatory
namecolumn based onaIsToBandbIsToAvalues.Changes
updateName()and added@PrePersistand@PreUpdatelisteners to auto-generate thename.RelationshipTypeTest.javawith unit test forupdateName()verifying the auto-naming behavior.namecolumn (required now thatnamecolumn cannot beNULL).Ticket
https://issues.openmrs.org/browse/TRUNK-5950
Checklist: I completed these to help reviewers :)
mvn clean packageright before creating this pull request and added all formatting changes to my commit.