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.
Allow user select eap version of JetBrains IDE #7852
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
Allow user select eap version of JetBrains IDE #7852
Changes from all commits
9266dc4
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.
this for loop is fairly complex, with many things happening in a single line - did you consider breaking it down a bit?
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: I would find it a bit "cleaner" to use a boolean like
option.useLatestImage
, and if it's true, setoption.latestImage
(just likeoption.resolveImageDigest
andoption.image
above).Here, we seem to use
option.latestImage
both as a "boolean" (i.e.filter(([_, x]) => x.latestImage))
above) and a resolved value.latestImage = await ...
. This looks a little bit dangerous (e.g. we might accidentally resolve the same image multiple times, or maybe forget to resolve it elsewhere, etc).However, not blocking the review due to this. Please feel free to address in a follow-up 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.
latestImage is a string not boolean, so
filter(([_, x]) => x.latestImage)
is equal thanfilter(([_, x]) => x.latestImage != null && x.latestImage !== '')
it no problem I think
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.
Thanks @iQQBot! Yes, I understand this, but my point was, I prefer something like this:
where the controlling condition is different from what's actually resolved.
Currently, the code seems to work like this:
This makes it a bit unclear if an image has already been resolved or not, e.g.:
if (!option.latestImage) { option.latestImage = await resolve(); }
option.latestImage === "latest"
, becauseif (option.latestImage)
looks "true")