search

ton-org / blueprint

TON development for professionals - all-in-one tool for writing, testing and deploying smart contracts
316 stars 51 forks source link

Separate .compile and wrapper files #110

Open a-bahdanau opened 1 month ago

a-bahdanau commented 1 month ago

It is not intuitive that compile file should be located in wrappers directory. Also it will be easier to setup workflow to share wrappers with someone(npm or just simple copypaste of wrappers dir)

krigga commented 1 month ago

Do you mean that there should be a separate directory, say compilables, that contains the .compile.ts files?

a-bahdanau commented 1 month ago

Yep, if it does not break some internals

krigga commented 3 weeks ago

I think the internals won't be broken, but we must make it so this change is backward compatible. One way I see is to add an optional field to the config, something like separateCompilables, which would be false by default (if not specified); then the new projects will be generated with a config with this field = true by default, and the old projects would still work fine.