Skip to content

Allow cli generation to configure bundle behaviour #52

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

Closed
iboss-ptk opened this issue Aug 13, 2022 · 3 comments
Closed

Allow cli generation to configure bundle behaviour #52

iboss-ptk opened this issue Aug 13, 2022 · 3 comments

Comments

@iboss-ptk
Copy link

Currently bundle has option to specify bundle files and scope but not available to cli.

It would be helpful if we can have --bundle-file, --bundle-scope

@pyramation
Copy link
Collaborator

pyramation commented Aug 13, 2022

should be fixed!

--bundle ## or --no-bundle
--bundleFile
--bundleScope

npm install -g @cosmwasm/[email protected]

@iboss-ptk I'd like to mention we should encourage programmatic usage, or find a way to use the TSBuilderOptions somehow. The CLI is going to move towards less recommended usage.

can you checkout https://github.com/CosmWasm/ts-codegen#programmatic-usage and see if there's a way to integrate this by creating a JSON of the TSBuilderOptions object?

@pyramation
Copy link
Collaborator

also @iboss-ptk in the future, I plan to (hopefully soon) do non-scoped bundles #49

the reason for scoped is so it puts everything neatly in one object (makes a nice combo with telescope), but for some pure contract projects, I think this pure non-scoped bundling will be nice. Keep an eye out for that issue when it comes out, I think will be nicer ;)

@iboss-ptk
Copy link
Author

Will check them out!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants