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

dfx extensions #1124

Closed
16 tasks done
Tracked by #80
lastmjs opened this issue Jul 27, 2023 · 0 comments · Fixed by #1759
Closed
16 tasks done
Tracked by #80

dfx extensions #1124

lastmjs opened this issue Jul 27, 2023 · 0 comments · Fixed by #1759
Labels
breaking change This PR contains a breaking change code cleanliness Product health, tech debt, etc. developer experience Speed, usability, shiny, wow-factor, customization

Comments

@lastmjs
Copy link
Member

lastmjs commented Jul 27, 2023

  • gzip and metadata #1029
  • Integrate azle into didc, dfx, and DFINITY Docs #626
  • use the new tech stack dfx.json feature
  • http should be the new default for candid
  • automatic and custom will have to be explicitly put into the azle dfx.json now
  • make sure to test post_install
  • Clean up the required dfx.json config for azle canisters using type: azle
  • make sure to keep all custom canisters
  • fix the global candid dir clashing issue...
  • whoami needs to be fixed, we need to figure out how to write the candid of your own canister to the filesystem of the canister...
  • remove all opt levels
  • think about the candid directory and if it's a good place for the candid files, what about naming collisions?
  • write all candid files in assets to the candid directory
  • make sure candid_gen is actually working and being respected
  • npx azle install-dfx-extension...should we keep this? should we have the user run this on their own? The problem is that if the try to start dfx in the same directory as an azle dfx.json, then they have to run this
  • make sure to check that the extension.json version is kept up-to-date with the azle version in release
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking change This PR contains a breaking change code cleanliness Product health, tech debt, etc. developer experience Speed, usability, shiny, wow-factor, customization
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant