feat: investigate a solution where immutable objects are created when a package is published #8736
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
…ge publishing and updating
|
The latest updates on your projects. Learn more about Vercel for GitHub. 6 Skipped Deployments
|
iota-ci
added
sc-platform
valeriyr
changed the title
Dkwcs
reviewed
Oct 3, 2025
| } | ||
| } | ||
| Err(err) => { | ||
| let object_runtime: &ObjectRuntime = context.object_runtime(); |
Contributor
There was a problem hiding this comment.
To be honest, it’s not fully clear for me, why we’re loading objects when error occurs.
I’m still getting familiar with doc, probably I’ll find an answer there, but it would be nice if you add minor clarification of this flow or something like (regular flow - this flow).
Contributor
|
Closed in favor of #9296 |
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.
Description of change
This PR shows how we can implement the idea of creating
AuthenticatorInfoV1instances during package publishing and updating.It shouldn't be considered as a solution; it is just a prototype.
Links to any relevant issues
fixes #8719