enso-org/enso
1
1
Fork 0
mirror of https://github.com/enso-org/enso.git synced 2024-12-23 18:34:03 +03:00
Code Issues Projects Releases Wiki Activity
09c4b7a993
enso/app/dashboard/tsconfig.json

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

23 lines
445 B
JSON
Raw Normal View History

Cognito auth 2/7 - add authorization app (#5798) 2nd PR for IDE/Cloud authorization with cognito. This PR introduces boilerplate react app + some amplify code to fetch the access token + username of the currently logged in user, if they are already authenticated. Registration + Login + Set Username + Forgot Password flows are to be added in next PRs to keep the changes reviewable.
2023-03-15 14:54:16 +03:00
{
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
"extends": "../tsconfig.json",
Support for creating and editing Data Links (#8882) - Close https://github.com/enso-org/cloud-v2/issues/734 - Add modal to create a new Data Link - Add the same input to the asset right panel - Add entries on context menu and Drive Bar - The shortcut is <kbd>Cmd</kbd>+<kbd>Shift</kbd>+<kbd>Alt</kbd>+<kbd>N</kbd> - Add (and use) corresponding backend endpoints # Important Notes - All UI is currently generated based off of a single-source-of-truth JSON Schema file. - JSON Schema was chosen for a few reasons: - trivial to parse (it's plain JSON) - sufficiently powerful (supports unions (used in the initial schema), objects, and singleton/literal types) - but still quite simple (this makes it easier to implement various utilities for, because there are fewer cases to cover) - Note that it is definitely possible to change this. The original suggestion was a TypeScript file, which can definitely be done even using just the `typescript` package itself - I just prefer to avoid adding another step in the build process, especially one that depends on the `typescript` package at runtime. - Note also that we *do* actually bundle transpilers as part of the visualization loading code in GUI2 - so for now at least, the size of the dependency isn't a primary concern, but rather just the mental overhead of having another dependency for this one specific task.
2024-02-12 13:05:30 +03:00
"include": [
Fix typechecking (#9279) - Fix issue where `playwright-report/` is being typechecked by `npm run typecheck` in the dashboard, causing CI to fail - Attempt to fix flaky dashboard test # Important Notes To test that typechecking isn't completely broken, it's recommended to intentionally create a type error in the dashboard code base.
2024-03-06 11:20:08 +03:00
"src",
"e2e",
Support for creating and editing Data Links (#8882) - Close https://github.com/enso-org/cloud-v2/issues/734 - Add modal to create a new Data Link - Add the same input to the asset right panel - Add entries on context menu and Drive Bar - The shortcut is <kbd>Cmd</kbd>+<kbd>Shift</kbd>+<kbd>Alt</kbd>+<kbd>N</kbd> - Add (and use) corresponding backend endpoints # Important Notes - All UI is currently generated based off of a single-source-of-truth JSON Schema file. - JSON Schema was chosen for a few reasons: - trivial to parse (it's plain JSON) - sufficiently powerful (supports unions (used in the initial schema), objects, and singleton/literal types) - but still quite simple (this makes it easier to implement various utilities for, because there are fewer cases to cover) - Note that it is definitely possible to change this. The original suggestion was a TypeScript file, which can definitely be done even using just the `typescript` package itself - I just prefer to avoid adding another step in the build process, especially one that depends on the `typescript` package at runtime. - Note also that we *do* actually bundle transpilers as part of the visualization loading code in GUI2 - so for now at least, the size of the dependency isn't a primary concern, but rather just the mental overhead of having another dependency for this one specific task.
2024-02-12 13:05:30 +03:00
"../types",
Move all user-facing text to a central location (#8831) - Closes https://github.com/enso-org/cloud-v2/issues/861 - Adds a `getText` function and React Context to abstract away all text that is shown to users The main immediate benefit is making all text much more discoverable - both being able to know of every piece of text used across the entire application, and making it a lot easier to refactor certain strings when needed rather than having to hunt for strings to replace (and potentially miss one). The longer term benefit is that this will make it easy to add localization, by simply adding another JSON file with the same keys as the existing one, and adding a little bit of logic. # Important Notes None
2024-03-25 11:13:24 +03:00
"./src/**/*.json",
Support for creating and editing Data Links (#8882) - Close https://github.com/enso-org/cloud-v2/issues/734 - Add modal to create a new Data Link - Add the same input to the asset right panel - Add entries on context menu and Drive Bar - The shortcut is <kbd>Cmd</kbd>+<kbd>Shift</kbd>+<kbd>Alt</kbd>+<kbd>N</kbd> - Add (and use) corresponding backend endpoints # Important Notes - All UI is currently generated based off of a single-source-of-truth JSON Schema file. - JSON Schema was chosen for a few reasons: - trivial to parse (it's plain JSON) - sufficiently powerful (supports unions (used in the initial schema), objects, and singleton/literal types) - but still quite simple (this makes it easier to implement various utilities for, because there are fewer cases to cover) - Note that it is definitely possible to change this. The original suggestion was a TypeScript file, which can definitely be done even using just the `typescript` package itself - I just prefer to avoid adding another step in the build process, especially one that depends on the `typescript` package at runtime. - Note also that we *do* actually bundle transpilers as part of the visualization loading code in GUI2 - so for now at least, the size of the dependency isn't a primary concern, but rather just the mental overhead of having another dependency for this one specific task.
2024-02-12 13:05:30 +03:00
"../../utils.ts",
Fix typechecking (#9279) - Fix issue where `playwright-report/` is being typechecked by `npm run typecheck` in the dashboard, causing CI to fail - Attempt to fix flaky dashboard test # Important Notes To test that typechecking isn't completely broken, it's recommended to intentionally create a type error in the dashboard code base.
2024-03-06 11:20:08 +03:00
".prettierrc.cjs",
"*.js",
"*.ts"
Support for creating and editing Data Links (#8882) - Close https://github.com/enso-org/cloud-v2/issues/734 - Add modal to create a new Data Link - Add the same input to the asset right panel - Add entries on context menu and Drive Bar - The shortcut is <kbd>Cmd</kbd>+<kbd>Shift</kbd>+<kbd>Alt</kbd>+<kbd>N</kbd> - Add (and use) corresponding backend endpoints # Important Notes - All UI is currently generated based off of a single-source-of-truth JSON Schema file. - JSON Schema was chosen for a few reasons: - trivial to parse (it's plain JSON) - sufficiently powerful (supports unions (used in the initial schema), objects, and singleton/literal types) - but still quite simple (this makes it easier to implement various utilities for, because there are fewer cases to cover) - Note that it is definitely possible to change this. The original suggestion was a TypeScript file, which can definitely be done even using just the `typescript` package itself - I just prefer to avoid adding another step in the build process, especially one that depends on the `typescript` package at runtime. - Note also that we *do* actually bundle transpilers as part of the visualization loading code in GUI2 - so for now at least, the size of the dependency isn't a primary concern, but rather just the mental overhead of having another dependency for this one specific task.
2024-02-12 13:05:30 +03:00
],
More E2E tests; `export default` classes from modules (#8730) This is a prerequisite for adding a CI action for E2E tests. - Fix E2E tests - Remove visual regression testing (VRT) and associated fixtures (screenshots) for now - Switch dashboard almost fully to Vite, from ESBuild, to match GUI2's build tooling. - Add some new E2E tests: - Creating assets - Deleting assets - Creating assets from the samples on the home page - Sort assets - Includes fixes for sorting: - Group sorted assets by type again (regression) (see https://github.com/enso-org/cloud-v2/issues/554) - Make sorting by title, case insensitive. This is because it is more intuitive for non-programmers if all items with uppercase names *aren't* separated from those with lowercase names - especially since the Windows FS is case-insensitive. - Normalization of Unicode letters is *not* currently being done. It can potentially be added later. - Double-clicking *anywhere* on a directory row now expands it. Previously it was only being expanded when double clicking - Add recursive label adding/removal to mirror backend - Note: The current implementation is not exactly the same as the backend's implementation. - Fix https://github.com/enso-org/cloud-v2/issues/872 - Unset "saved project details" (for opening the last open project) if fetching it produces an error. # Important Notes - All tests pass. (run `npm run test:e2e` in `app/ide-desktop/lib/dashboard`) - All `npm` commands should be run in `app/ide-desktop/lib/dashboard`. `dashboard:*` npm scripts have been removed from `app/ide-desktop` to prevent a mess. - `npm run dev` confirmed to still work. Note that it has not been changed as it was already using Vite. - `npm run build` now uses `vite build`. This has been tested using a local HTTP server that supports `404.html`. - Other cases have been tested: - `npm run test:e2e` works (all tests pass) - `./run ide build` works - `./run ide watch` works - `./run ide2 build` works - `./run gui watch` works
2024-01-31 14:35:41 +03:00
"exclude": ["./dist"],
[Gui2] Opening projects and language server connection (#7813) # Important Notes - Binary LS endpoint is not yet handled. - The parsing of provided source is not entirely correct, as each line (including imports) is treated as node. The usage of actual enso AST for nodes is not yet implemented. - Modifications to the graph state are not yet synchronized back to the language server.
2023-09-22 06:43:25 +03:00
"compilerOptions": {
"composite": true,
"noEmit": false,
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
"outDir": "../../node_modules/.cache/tsc",
Re-organize `lib/dashboard/` (#8587) - Significantly flattens directory structure of `lib/dashboard/` # Important Notes - Basic testing done on: - dashboard's `npm run dev` which (since quite recently) uses Vite. - specifically: `npm run dev` in `app/ide-desktop/lib/dashboard`, OR `npm run dashboard:dev` in `app/ide-desktop` - dashboard's bundle script (`npm run build`) which uses ESBuild. - GUI2's own entry point (GUI2's `npm run dev`). - `./run ide build` - `./run ide watch` - `./run ide2 build` - `./run gui watch`
2024-01-10 19:22:11 +03:00
"paths": { "#/*": ["./src/*"] },
Improve Invitation flow (#9928) #### Tl;dr Closes: enso-org/cloud-v2#1186 This PR significantly improves the invitation UX and add ability to view/resend/copy/delete invitations <details><summary>Demo Presentation</summary> <p> https://github.com/enso-org/enso/assets/61194245/62124243-50ce-47e1-bcac-789463b5e755 </p> </details> --- #### Context: #### This Change: What the change does in the larger context? Specific details to highlight for review: 1. Redesign the Invitation dialog 2. Add the ability to edit emails after typing ` ` 3. Adds ability to use different separators: `<space>`, `<semicolon>`, `<colon>` or `<newline>` 4. Shows Invitation on the `members` page in settings. 5. Adds ability to remove, resend, copy or delete invitations 6. Improve the UI of dialogs, buttons #### Test Plan: Go over how you plan to test it. Your test plan should be more thorough the riskier the change is. For major changes, I like to describe how I E2E tested it and will monitor the rollout. ---
2024-05-22 21:26:02 +03:00
"target": "ESNext",
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
"lib": ["ESNext", "DOM", "DOM.Iterable", "ES2023"]
[Gui2] Opening projects and language server connection (#7813) # Important Notes - Binary LS endpoint is not yet handled. - The parsing of provided source is not entirely correct, as each line (including imports) is treated as node. The usage of actual enso AST for nodes is not yet implemented. - Modifications to the graph state are not yet synchronized back to the language server.
2023-09-22 06:43:25 +03:00
}
Cognito auth 2/7 - add authorization app (#5798) 2nd PR for IDE/Cloud authorization with cognito. This PR introduces boilerplate react app + some amplify code to fetch the access token + username of the currently logged in user, if they are already authenticated. Registration + Login + Set Username + Forgot Password flows are to be added in next PRs to keep the changes reviewable.
2023-03-15 14:54:16 +03:00
}
Reference in New Issue Copy Permalink