You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The server infrastructure of Total re-generates the client JS code
on the fly by invoking dartc. There are 2 issues with this:
Some people might want to use frog
The path specified is Linux specific - running on a mac requires a different path.
One idea is to take the auto-regeneration feature out and replace it with a mechanism that compiles the client code once before the server is started. Another is to make the server flexible enough to support frog or dartc, and support them on differnt environments.
I think we are touting the dart editor for a compile/edit/debug cycle, so what I'm going to do first is try that out and document it. If that works, then I'll remove the compile meechanism from the server.
The text was updated successfully, but these errors were encountered:
This is a minor change with just bug fixes:
* Handle trailing commas in for-loop updaters (#1354).
* Format `||` patterns like fallthrough cases in switch expressions (#1602).
* Handle comments and metadata before variables more gracefully (#1604).
* Ensure comment formatting is idempotent (#1606).
* Better indentation of leading comments on property accesses in binary operator
operands (#1611).
* Don't crash on doc comments in local variable declarations (#1621).
This won't affect much code, but it does change the formatting in some cases.
Change-Id: I2d52fee92aecbc24315e4f1a89360af85ec85942
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/401482
Auto-Submit: Bob Nystrom <[email protected]>
Commit-Queue: Alexander Thomas <[email protected]>
Reviewed-by: Alexander Thomas <[email protected]>
This issue was originally filed by [email protected]
The server infrastructure of Total re-generates the client JS code
on the fly by invoking dartc. There are 2 issues with this:
One idea is to take the auto-regeneration feature out and replace it with a mechanism that compiles the client code once before the server is started. Another is to make the server flexible enough to support frog or dartc, and support them on differnt environments.
I think we are touting the dart editor for a compile/edit/debug cycle, so what I'm going to do first is try that out and document it. If that works, then I'll remove the compile meechanism from the server.
The text was updated successfully, but these errors were encountered: