DFX 0.18.0 is promoted!

You can read the release notes here.

This release removed some deprecated items. Please check the migration guide.

The bundled Motoko compiler was upgraded to v0.11.0. Please check this guide for more information.

Please let us know if you run into any problems.

11 Likes

This release includes a preview feature dfx canister logs.

We have noticed that it is not working as expected. The fix PR is pending.

2 Likes

Hello.
I am trying to update my application (Motoko based).
I switch my app to use base@0.11.0 version (Mops⠀•⠀Motoko Package Manager)
I’ve executed various updates to apply instrruction but one warning is still here.

WARN: .mops/base@0.11.0/src/Principal.mo:80.20-80.32: warning [M0154], field append is deprecated:
Array.append copies its arguments and has linear complexity;

For now I can ignore it.

It’s safe to ignore that warning - this should not be new behaviour either.

We are considering turning off warnings for imported packages, since there’s not much you can do about them,

1 Like

ok, thank you for the update.
I’ve managed to migrate my apps and remove all warnings except this one

1 Like

Candid assist getting a lot of love on Twitter.

Thanks @chenyan and everyone who helped drive this tool forward to make Candid more accessible!

7 Likes

I noticed that if your canister has a nullable single entry, that the candid assist doesn’t activate and it assumes null. Could we get this fixed? Or a flag to activate it? @chenyen

Yeah, I thought about it. Always enabling this will be a breaking change, specifically, it will pop up every time when installing the asset canister. Maybe a flag like --always-assist?

That would be great. Unless dfx could look at the type and determine it is an asset canister(type: assets).

Stupid question: How do you activate the principal auto-fill in the new DFX candid widget? I’m banging all over my keyboard and can’t figure it out.

You can type in a prefix of the identity name and press “tab”. I will try to add that to the prompts.

@chenyan Is this intended behavior?

Notice that 50555054 is supposed to be TPUP, but it outputs PUPT for memo.

From left to right, 50 – P, 55 – U, 50 – P, 54 – T. Am I missing something?

Sorry…I guess Rust is really this wacky?

I naively copied it. :man_facepalming:

I guess rust engineers think backwards or something. :wink:

1 Like

:sweat_smile: Let me ask internally.