Skip to content

Update anchor.workspace program names to use camelCase#4662

Open
acheroncrypto wants to merge 5 commits into
otter-sec:masterfrom
acheroncrypto:update-anchor.workspace-program-names-to-use-camelCase
Open

Update anchor.workspace program names to use camelCase#4662
acheroncrypto wants to merge 5 commits into
otter-sec:masterfrom
acheroncrypto:update-anchor.workspace-program-names-to-use-camelCase

Conversation

@acheroncrypto

Copy link
Copy Markdown
Collaborator

Problem

anchor.workspace has supported camelCase program names instead of the legacy PascalCase since v0.29 (#2579), and the default templates also use camelCase by default since v0.31 (#3581).

PascalCase field accessors are unconventional, and IIRC it's the only place in our entire SDK that required it. New code should use camelCase for consistency.

Summary of changes

Update anchor.workspace program names to be camelCase in:

  • Docs
  • Examples
  • Tests

Note: PascalCase support is still continued; this PR does not touch the TS package.

@vercel

vercel Bot commented Jun 11, 2026

Copy link
Copy Markdown

@acheroncrypto is attempting to deploy a commit to the OtterSec Team on Vercel.

A member of the Team first needs to authorize it.

@acheroncrypto acheroncrypto added documentation Improvements or additions to documentation examples tests fix Bug fix PR labels Jun 11, 2026
@swaroop-osec

Copy link
Copy Markdown
Collaborator

Nice cleanup.
One gap: this only updates docs/, but the new docs-v2/ site (added in #4460) has the same pages under docs-v2/src/content/docs/v1/ still using PascalCase. Worth converting those too for consistency.

@0x4ka5h

0x4ka5h commented Jun 12, 2026

Copy link
Copy Markdown
Collaborator

Yeah, I agree with @swaroop-osec on this aswell.

@acheroncrypto

Copy link
Copy Markdown
Collaborator Author

Updated, but why are v2 docs in master and not anchor-next?

@swaroop-osec swaroop-osec left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation examples fix Bug fix PR Merge tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants