Re-host the dart web UI on v3 of the server protocol

[devoncarew]

• re-host the dart web UI on v3 of the server protocol

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

• See our contributor guide for general expectations for PRs.
• Larger or significant changes should be discussed in an issue before creating a PR.
• Contributions to our repos should follow the Dart style guide and use dart format.
• Most changes should add an entry to the changelog and may need to rev the pubspec package version.
• Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

[devoncarew]

@johnpryan - no hurry on this; I'll likely have some questions about the workshops UI and testing mode code before landing this.

[johnpryan]

It would be good to keep the diagnostic messages and the test code features working for now. Is that something you can do in this PR?

[devoncarew]

Updated! What's a good way to test the codelabs locally?

[johnpryan]

You can test the codelabs and workshops by loading the right URL. For example:

To test a workshop you can click on one of the links in the README and copy-paste the URL after the /. For example: localhost:8080/workshops.html?webserver=https://dartpad-workshops-io2021.web.app/inherited_widget

To test a codelab you can right-click and grab the src attribute on the embedded DartPad iframe from the codelab such as the Basic Flutter layout concepts codelab, and do the same thing. For example http://localhost:8080/embed-flutter.html?theme=dark&run=false&split=60&ga_id=false

[johnpryan]

You can also verify the embeds are working using the example at http://localhost:8080/example/embed.html

[devoncarew]

It would be good to keep the diagnostic messages and the test code features working for now. Is that something you can do in this PR?

I can definitely add back in the test code features - I'd assumed from reading through the code that it wasn't used, but was mistaken.

Do you think the diagnostic messages functionality is important? It's not currently exposed in the new UI, and I wasn't really planning to do it. I think it's useful for more sophisticated diagnostics in an IDE, but I don't think critical here.

[johnpryan]

Do you think the diagnostic messages functionality is important?

IIRC this was to enable corrections and documentation links: #1676

[devoncarew]

I restored the contextMessages info and related UI; this PR still needs some manual testing through the codelabs and embeds.

[johnpryan]

this PR still needs some manual testing through the codelabs and embeds.

I'm seeing an issue with all three versions where the analysis message is always the same:

[devoncarew]

I'm seeing an issue with all three versions where the analysis message is always the same:

The protocol changed a bit in this PR (due to the inclusion context messages and changing how we stored location info on analysis issues); you'll need to run this against a local backend to see results.

That's a good reminder though; we may want to land the dart-services + sketchpad portion of this PR first, and follow up ~an hour later with the part moving the current UI over to the new backend.

[devoncarew]

Codelabs and the tests UI both seem to be working (responding to the server, showing analysis issues, supporting run, ...).

[johnpryan]

We might want to update CONTRIBUTING.md and other readme files to remove any references to protoc

[devoncarew]

We might want to update CONTRIBUTING.md and other readme files to remove any references to protoc

👍 ; I'd like to do that in a follow-up (this PR has accumulated a bunch of changes).

I'll hold this PR until we determine the build issue with the master channel (we'll need that server to support the new protocol).

[johnpryan]

I'll hold this PR until we determine the build issue with the master channel (we'll need that server to support the new protocol).

The checks on the main branch of the repo are passing, it's only the Cloud Run deploy action for the Flutter main channel that's failing so this should be okay to merge.

[devoncarew]

The checks on the main branch of the repo are passing, it's only the Cloud Run deploy action for the Flutter main channel that's failing so this should be okay to merge.

I think the checks were unintentionally all run against stable (which passed happily). The regression on main has now made its way to beta.