Does the makecode integration still works?

[Karlo-Emilo]

A collaborator has reported that he gets an error message when exporting to Makecode.

I do not have a micro:bit at hand (I am travelling), so I have not been able to test it myself.

[Karlo-Emilo]

Can we somehow reuse micro:bit's MakeCode integration?

[r59q]

I just tested the integration(on the main branch). I have no issues using the v2.20 micro:bit.
However I'm not sure what you mean by 'exporting' to makecode? This is not a functionality we provide, it might be a misunderstanding? There's an issue where you cannot use both makecode and ML-Machine at the same time, otherwise the bluetooth connection gets a bit funky, this has always been the case. According my knowledge and testing there hasn't been a regression. But it could certainly help with some improvements
I think using the other MakeCode integration is a good idea.

[Karlo-Emilo]

[Karlo-Emilo]

@jaustin, some Americans experience this error (see the image above) when using our MakeCode extension, but we are unable to reproduce it. Do you have any idea about what the issue could be?

[r59q]

Let's see if #643 fixes the issue.

I'm not at all sure what could cause this issue, and I'm not entirely sure the embedded integration would fix this issue... One approach to solve the issue could be to use a "injected" extension instead of using the extension system. If we instead just add the code for the extension to the project instead of using an extension we might work around the issue.

Unless I am able to replicate it your guess is as good as mine, but i hope we can alleviate the issue by making the embedded integration, but we would have to investigate after it's finished