Move typespec into sdk/core #3174
Draft
Conversation
This file contains hidden or 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
Because typespec is just an implementation detail of core, and to help simplify upcoming eng-sys changes that should make publishing easier, move all the typespec crates under sdk/core.
|
@Hallir @danieljurek we talked about this a few days ago - that it should allow us to calculate the dependency order for all "core" crates. Do we want to move forward with this then? The sooner the better, because I have a few more core changes to make. It shouldn't affect anyway because we use workspace dependencies, and I did grep the repo (excluding |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Because typespec is just an implementation detail of core,
and to help simplify upcoming eng-sys changes that should make publishing easier,
move all the typespec crates under sdk/core.