Update polkadot deps to support xt v5 and refactor code to handle new private identifiers #145
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.
Closes #141
After the update in #142, we got several errors like "Cannot read private field". This is because private fields were introduced in the meantime in JS and Vue or Pinia-stores strip them under certain circumstances.
Do not store complex objects in the store if possible (e.g. the worker).
When handling reactive objects declared with
refwe do:shieldingTargetApi.value = markRaw(api);toRaw(notesBucketInfo). Note: simple things likeOption.unwrap()need internal private state.Other changes:
Tested: