-
Notifications
You must be signed in to change notification settings - Fork 327
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
Re-organize lib/dashboard/
#8587
Conversation
restructure finished! the new directory structure might not be perfect, but i think this is probably worth merging regardless? but anyway, given that it should be more or less complete, i'm now beginning to test using the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The /app/gui2 part looks good.
not sure why there was a merge error, automatic merged worked fine locally. |
Basic testing re-done on all cases after merge. |
This is required because `index.ts` was renamed to `entrypoint.ts` in order to avoid colliding with the main export of the `enso-dashboard` module, which is used by `gui2` as `dashboard.run()`. This file was renamed in #8587, causing the issue. Build script changes also included thanks to @mwu-tow. # Important Notes This should only affect projects opened against the remote (cloud) backend, meaning that to test this, you should open a project against the cloud backend.
Pull Request Description
lib/dashboard/
Important Notes
npm run dev
which (since quite recently) uses Vite.npm run dev
inapp/ide-desktop/lib/dashboard
, ORnpm run dashboard:dev
inapp/ide-desktop
npm run build
) which uses ESBuild.npm run dev
)../run ide build
./run ide watch
./run ide2 build
./run gui watch
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:
The documentation has been updated, if necessary.Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
Unit tests have been written where possible.If GUI codebase was changed, the GUI was tested when built using./run ide build
.