-
Notifications
You must be signed in to change notification settings - Fork 91
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
Asset : Added Test For AssetInSameState #429
base: develop
Are you sure you want to change the base?
Conversation
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.
Please check for both the instances
- When instance-id is provided and asset is in same state,
- When instance-id is not provided, then change status of asset itself, but the given new status is of same status of existing asset.
Above must be done for both status_change & vc_status_change.
So totally 4 places to check the error-code AssetInSameState
.
This reverts commit 9255758.
Hey @vatsa287 , I hope I have completed your required changes |
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.
Few minor comments
Hey @vatsa287 , I have made the changes , Please review the PR |
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.
Hoping you have gone through this discussion, please start contributing on next level issues other than good-first-issues
.
Hello @amarts , can you please review the PR |
LGTM. @zeel991 need to resolve the merge conflicts. |
Done ! |
Hello @amarts sir ,PTAL |
AssetInSameState
#381AssetInSameState