chore: revert sdk.envs field#9559
Merged
Merged
Conversation
This moved location sometime ago - it shouldn't be here. Signed-off-by: Justin Chadwell <me@jedevc.com>
Reverting this temporarily, we still need more design discussion around this, there's still some things to work out. But ideally, we shouldn't block the release. Signed-off-by: Justin Chadwell <me@jedevc.com>
Contributor
|
also need to regenerate docs/sdk, but looks good otherwise. |
Contributor
Author
|
Shouldn't need to? No details of the |
marcosnils
approved these changes
Feb 11, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Follow-up to, and partial reversion of #9454.
Reverting this temporarily, we still need more design discussion around this, there's still some things to work out. But ideally, we shouldn't block the release.
We keep the struct-ification of the
sdkfield though, that's useful, since we intend to extend that withpinand friend in the future: see #9156.