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
fix: change mdcoverage url for getCurrentApiVersion #1191
fix: change mdcoverage url for getCurrentApiVersion #1191
Changes from all commits
8616e0c
f4ca015
3a72903
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.
If we're taking that approach, maybe
https://org62.my.salesforce-sites.com/services/data
would be more reliable/scalable than this team's endpoint.or use
Promise.any
of several known URLsThere 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.
why version 58.0 as default?
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.
I just chose a recent one. It's better than throwing an error. We really should never get to this point. ComponentSets should have apiVersion and sourceApiVersion set by the consumer.
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.
At some point version 58.0 will be too old and things may not function as expected on this version. In that case does it make sense to throw an error vs using a default value that is old?
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.
The code will warn with the
missingApiVersion
message should it ever get to this point and use v58.0, so if an end user sees this message they can do things to get better results should it fail. If we throw, they will definitely need to do something to get it to work. Both Shane and I felt that doing what we could to not fail is better.In practice, the checks for an API version should never get past the
sourceApiVersion
andapiVersion
set on theComponentSet
. If users of SDR are creating ComponentSets without setting asourceApiVersion
and/orapiVersion
then they shouldn't be creating a manifest from it.