Sm/qa-schemas-updates #1066
Closed
Sm/qa-schemas-updates #1066
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
||
| Messages.importMessagesDirectory(__dirname); | ||
| const messages = Messages.loadMessages('@salesforce/core', 'scratchOrgInfoGenerator'); | ||
| export const messages = Messages.loadMessages('@salesforce/core', 'scratchOrgInfoGenerator'); |
| unpackagedMetadata?: { path: string }; | ||
| seedMetadata?: { path: string }; | ||
| }; | ||
| export type PackageDir = PackageDirFromSchemas; |
There was a problem hiding this comment.
maybe add a comment to remove in the next major, and have dependencies rely on the /schemas instead?
|
in favor of #1081 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What does this PR do?
schemasrepoWhat issues does this PR fix or reference?
QA and "implementaiton" for forcedotcom/schemas#85
to fix @W-13565856@ and https://github.com/forcedotcom/sfdx-core/issues/489
[this could be a breaking change--this PR is meant to help find out what these type changes could break downstream of sfdx-core, and also to give the QA-er a starting point for playing with the types]