-
Notifications
You must be signed in to change notification settings - Fork 9
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
Edit Dialog #158
Edit Dialog #158
Conversation
A JIRA Issue ID is missing from your branch name! 🦄 Your branch: editdialog If this is your first time contributing to this repository - welcome! Please refer to jira-lint to get started. Without the JIRA Issue ID in your branch name you would lose out on automatic updates to JIRA via SCM; some GitHub status checks might fail. Valid sample branch names:‣ feature/shiny-new-feature--mojo-10' |
Codecov Report
@@ Coverage Diff @@
## dev #158 +/- ##
==========================================
+ Coverage 46.32% 46.42% +0.10%
==========================================
Files 109 110 +1
Lines 2053 2070 +17
Branches 463 463
==========================================
+ Hits 951 961 +10
- Misses 1020 1027 +7
Partials 82 82
Continue to review full report at Codecov.
|
@sdevalapurkar I addressed your comments from the closed PR, with the exception of the error dialog. I will handle that in the next PR along with the axios call and adding the test for the Edit Dialog. |
A JIRA Issue ID is missing from your branch name! 🦄 Your branch: editdialog If this is your first time contributing to this repository - welcome! Please refer to jira-lint to get started. Without the JIRA Issue ID in your branch name you would lose out on automatic updates to JIRA via SCM; some GitHub status checks might fail. Valid sample branch names:‣ feature/shiny-new-feature--mojo-10' |
A JIRA Issue ID is missing from your branch name! 🦄 Your branch: editdialog If this is your first time contributing to this repository - welcome! Please refer to jira-lint to get started. Without the JIRA Issue ID in your branch name you would lose out on automatic updates to JIRA via SCM; some GitHub status checks might fail. Valid sample branch names:‣ feature/shiny-new-feature--mojo-10' |
); | ||
|
||
expect(baseElement).toMatchSnapshot(); | ||
}); |
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.
we need to add a test case for when the Yes button is clicked and the onSave is called I think
possibly also for oncancel
} = props; | ||
|
||
const history = useHistory(); | ||
|
||
const openModalEdit = () => { |
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.
tests for all these probably need to be added as well, but not a blocker for this PR
A JIRA Issue ID is missing from your branch name! 🦄 Your branch: editdialog If this is your first time contributing to this repository - welcome! Please refer to jira-lint to get started. Without the JIRA Issue ID in your branch name you would lose out on automatic updates to JIRA via SCM; some GitHub status checks might fail. Valid sample branch names:‣ feature/shiny-new-feature--mojo-10' |
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.
lgtm when nick is happy with it, will let him give final approval
A JIRA Issue ID is missing from your branch name! 🦄 Your branch: editdialog If this is your first time contributing to this repository - welcome! Please refer to jira-lint to get started. Without the JIRA Issue ID in your branch name you would lose out on automatic updates to JIRA via SCM; some GitHub status checks might fail. Valid sample branch names:‣ feature/shiny-new-feature--mojo-10' |
A JIRA Issue ID is missing from your branch name! 🦄 Your branch: editdialog If this is your first time contributing to this repository - welcome! Please refer to jira-lint to get started. Without the JIRA Issue ID in your branch name you would lose out on automatic updates to JIRA via SCM; some GitHub status checks might fail. Valid sample branch names:‣ feature/shiny-new-feature--mojo-10' |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Overview
Links to jira tickets
This PR contains the following changes
This PR contains the following types of changes
Checklist
A list of items that are good to consider when making any changes.
Note: this list is not exhaustive, and not all items are always applicable.
General
Code
Style
Documentation
Tests
Linting/Formatting
See the
lint
commands in package.jsonSee the
format
commands in package.jsonSonarCloud
How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Screenshots
Please add any relevant UI screenshots, if applicable.