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

Get rid of Candid files if possible, put them in the .azle directory along with the other generated files #1753

Open
Tracked by #1722
lastmjs opened this issue Apr 19, 2024 · 0 comments

Comments

@lastmjs
Copy link
Member

lastmjs commented Apr 19, 2024

It seems best to take care of dfx extensions first, as it will be less of a burden on everyone: #1124

Candid and its generated files are possibly confusing to new developers, and I believe are generally an unnecessary extra concept especially when dealing with HTTP canisters.

Let's remove candid files from the developer's project by default for HTTP canisters...we'll put them in .azle somewhere. Let's consider if we should do this for all canisters by default, and maybe only put it in their directory if they specify the candid property differently in their dfx.json.

In fact, maybe dfx extensions is a prerequisite to this. I will think about that.

@lastmjs lastmjs mentioned this issue Apr 19, 2024
91 tasks
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

1 participant