Draft
Conversation
Collaborator
Author
|
@GlenDC by having it behind a cfg flag we can start using this internally already to confirm all the internals work as expected. Do you agree with this approach? Also should we enable this for some tests in CI, if so how without duplicating all of them? Once we figured out details I will finish this PR, and it can be review. No point in reviewing it before that, except for to get high level idea of what I'm doing here |
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
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.
Use new extensions when extensions_new cfg is enabled. This still uses the old API but is meant so we (and maybe other people) can try new extension storage logic.
After some time has passed and no issues popped up the goal is to migrate completely to the new stack and also start using the new API and features (&self, multiple copies...)