docs: flag pre-Cadence 1.0 syntax in fcl.mutate example#2807
Merged
Conversation
The transaction snippet in the fcl.mutate example uses AuthAccount, account.borrow, and a private path — all replaced in Cadence 1.0 with auth(...) &Account, account.storage.borrow, and storage-only paths. This commit only adds a note calling out the discrepancy; rewriting the snippet requires knowing the current Profile demo contract's storage path, which is outside this README's scope.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
peterargue
approved these changes
Apr 24, 2026
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
2 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.
Summary
The `fcl.mutate` code snippet in the README (lines 125–133) uses pre-Cadence 1.0 syntax that no longer compiles against current Cadence:
This PR only adds a `> Note:` callout above the code block pointing readers to the Cadence migration guide. It does not rewrite the snippet itself, because writing a correct 1.0 replacement requires knowing the current Profile demo contract's storage path (which may have changed).
A follow-up PR can replace the snippet with a current working example once the Profile demo contract's API is confirmed.
Test plan