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
[New Platform] Validate config upfront #35453
[New Platform] Validate config upfront #35453
Changes from 11 commits
c8f3ce6
1d37d47
0b9d5a8
532089a
4d805ad
001efc6
a09520b
75d01ee
1c3dfa7
924fc22
be8dc61
c0a98eb
4b582d1
be4e4d3
09cf5f2
19c02c4
e622cd3
f90711a
12d9947
2a01ed7
1345904
48c99cb
b8cc18a
de341ac
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
This file was deleted.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
issue: I believe this test will pass even if you change
rejects
toresolves
since you don'tawait
onexpect
😉 And in test below.Actually I'm surprised that we don't have any automatic linter-like check for cases like this :/
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.
alright, I expected that jest marks test as async if I call
rejects/resolves
in assertionThere 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.
linter rule is not implemented 😞 jest-community/eslint-plugin-jest#54
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.
Eh, too bad
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.
nit:
configPath
--->path
asconfig
part seems to be obvious here?I don't have a strong opinion on the name, but curious if we can be a tad more consistent and have something like this instead (here and maybe everywhere else)?
When you simplify config handling in the follow-ups we'll be able to drop
DevConfig
completely.But at the same time I understand that you want it to look the same as we do it for plugins, so I'm torn on this one