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.
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
Issue/8676 scmainvm tests #9142
Issue/8676 scmainvm tests #9142
Changes from 7 commits
b981ff9
b52a5ba
b247abf
bb51825
fdf52bb
4bb181c
94a894b
2002247
464757c
73dda08
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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'd be great if we can use the current constants in
NewSiteCreationMainVM
for these strings to avoid tests going out of sync with the VM. I believe making those public is the lesser of two evils here and there is a big risk with having them public. What do you think?Note that this is for
key_site_creation_state
,key_current_step
andkey_site_creation_state
string values. I am keeping all this to a single comment.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.
Yep, I was thinking about this for some time. I miss "package" scope so much :(. The reason why I felt like it's better to hardcode it in tests is that having them public "pollutes" autocomplete and we can't push anything to the develop without a working unit tests anyway. However, I don't feel strongly about it - updated in 464757c