Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs: how to rename and move contracts around in Blueprint-based and other projects #1628

Open
novusnota opened this issue Jan 29, 2025 · 0 comments
Assignees
Labels
docs: Book /book section of the docs: Guides, Cheatsheets, and a streamlined sequence of educational materials kind: docs Documentation for docs.tact-lang.org kept in docs folder
Milestone

Comments

@novusnota
Copy link
Member

For Blueprint it's mainly controlled in wrappers/ContractName.compile.ts (or similar for the case of compilables/).

For non-Blueprint projects, everything is controlled via a tact.config.json.

This stuff should go to the compilation page. In addition, a follow-up to #1112 is needed — a brief mention of wrappers vs. compilables/.

@novusnota novusnota added docs: Book /book section of the docs: Guides, Cheatsheets, and a streamlined sequence of educational materials kind: docs Documentation for docs.tact-lang.org kept in docs folder labels Jan 29, 2025
@novusnota novusnota self-assigned this Jan 29, 2025
@novusnota novusnota added this to the Doc: 2025-02 milestone Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs: Book /book section of the docs: Guides, Cheatsheets, and a streamlined sequence of educational materials kind: docs Documentation for docs.tact-lang.org kept in docs folder
Projects
None yet
Development

No branches or pull requests

1 participant