-
Notifications
You must be signed in to change notification settings - Fork 226
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
HTML-746: Removed onset and end dates from conditions tag. #196
Draft
icrc-loliveira
wants to merge
23
commits into
openmrs:master
Choose a base branch
from
icrc-loliveira:HTML-746
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
icrc-loliveira
changed the title
HTML-746: Removed onset and end dates from conditions.
HTML-746: Removed onset and end dates from conditions tag.
Aug 14, 2020
Thanks for the progress on this,you can also checkout this link to make a better pr https://wiki.openmrs.org/display/docs/Pull+Request+Tips |
Formatting.
…oliveira/openmrs-module-htmlformentry into HTML-746 � Conflicts: � api-2.3/src/main/java/org/openmrs/module/htmlformentry/ConditionElement.java � api-2.3/src/test/java/org/openmrs/htmlformentry/element/ConditionElementTest.java � api-2.3/src/test/java/org/openmrs/htmlformentry/element/ConditionTagTest.java
…module-htmlformentry into HTML-747 � Conflicts: � api-2.3/src/test/java/org/openmrs/htmlformentry/element/ConditionTagTest.java
…module-htmlformentry into HTML-746 � Conflicts: � api-2.3/src/test/java/org/openmrs/htmlformentry/element/ConditionTagTest.java
…module-htmlformentry into HTML-747 � Conflicts: � api-2.3/src/main/java/org/openmrs/module/htmlformentry/ConditionElement.java � api-2.3/src/test/java/org/openmrs/htmlformentry/element/ConditionTagTest.java
…module-htmlformentry into HTML-746 � Conflicts: � api-2.3/src/main/java/org/openmrs/module/htmlformentry/ConditionElement.java � api-2.3/src/test/java/org/openmrs/htmlformentry/element/ConditionTagTest.java
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Issue I worked on
see https://issues.openmrs.org/browse/HTML-746
Checklist: I completed these to help reviewers :)
My pull request only contains ONE single commit
(the number above, next to the 'Commits' tab is 1).
No? -> read here on how to squash multiple commits into one
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 --amend
I 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
I ran
mvn clean package
right before creating this pull request andadded all formatting changes to my commit.
No? -> execute above command
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.
My pull request is based on the latest changes of the master branch.
No? Unsure? -> execute command
git pull --rebase upstream master