mirror of
https://github.com/enso-org/enso.git
synced 2024-12-23 10:21:41 +03:00
e5b85bf16e
In a sequence of value-level operators, whitespace does not affect relative precedence. Functional operators still follow the space-precedence rules. The "functional" operators are: `>> << |> |>> <| <<| : .`, application, and any operator containing `<-` or `->`. All other operators are considered value-level operators. Asymmetric whitespace can still be used to form *operator sections* of value-level operators, e.g. `+2 * 3` is still equivalent to `x -> (x+2) * 3`. Precedence of application is unchanged, so `f x+y` is still equivalent to `f (x + y)` and `f x+y * z` is still equivalent to `(f (x + y)) * z`. Any attempt to use spacing to override value-level operator precedence will be caught by the new enso linter. Mixed spacing (for clarity) in value-operator expressions is allowed, as long as it is consistent with the precedences of the operators. Closes #10366. # Important Notes Precedence warnings: - The parser emits a warning if the whitespace in an expression is inconsistent with its effective precedence. - A new enso linter can be run with `./run libraries lint`. It parses all `.enso` files in `distribution/lib` and `test`, and reports any errors or warnings. It can also be run on individual files: `cargo run --release --bin check_syntax -- file1 file2...` (the result may be easier to read than the `./run` output). - The linter is also run as part of `./run lint`, so it is checked in CI. Additional language change: - The exponentiation operator (`^`) now has higher precedence than the multiplication class (`*`, `/`, `%`). This change did not affect any current enso files. Library changes: - The libraries have been updated. The new warnings were used to identify all affected code; the changes themselves have not been programmatically verified (in many cases their equivalence relies on the commutativity of string concatenation). |
||
|---|---|---|
| .. | ||
| .vscode | ||
| e2e | ||
| mock | ||
| parser-codegen | ||
| project-manager-shim-middleware | ||
| public | ||
| rust-ffi | ||
| scripts | ||
| shared | ||
| src | ||
| stories | ||
| templates | ||
| ydoc-server | ||
| .gitignore | ||
| .prettierignore | ||
| .prettierrc.json | ||
| .snyk | ||
| env.d.ts | ||
| env.story.d.ts | ||
| eslint.config.js | ||
| histoire.config.ts | ||
| index.html | ||
| lib0-ext.d.ts | ||
| LICENSE | ||
| package.json | ||
| playwright.config.ts | ||
| README.md | ||
| shortcuts.md | ||
| tsconfig.app.json | ||
| tsconfig.app.vitest.json | ||
| tsconfig.json | ||
| tsconfig.node.json | ||
| tsconfig.scripts.json | ||
| tsconfig.server.json | ||
| tsconfig.server.vitest.json | ||
| tsconfig.story.json | ||
| vite.config.ts | ||
| vite.ydoc-server-polyglot.config.ts | ||
| vitest.config.ts | ||
enso-ide
This template should help get you started developing with Vue 3 in Vite.
Recommended IDE Setup
VSCode + Volar (and disable Vetur) + TypeScript Vue Plugin (Volar).
Type Support for .vue Imports in TS
TypeScript cannot handle type information for .vue imports by default, so we replace the tsc CLI with vue-tsc for type checking. In editors, we need TypeScript Vue Plugin (Volar) to make the TypeScript language service aware of .vue types.
If the standalone TypeScript plugin doesn't feel fast enough to you, Volar has also implemented a Take Over Mode that is more performant. You can enable it by the following steps:
- Disable the built-in TypeScript Extension
- Run
Extensions: Show Built-in Extensionsfrom VSCode's command palette - Find
TypeScript and JavaScript Language Features, right click and selectDisable (Workspace)
- Run
- Reload the VSCode window by running
Developer: Reload Windowfrom the command palette.
Customize configuration
See Vite Configuration Reference.
Project Setup
pnpm install
Compile and Hot-Reload for Development
npm run dev
Type-Check, Compile and Minify for Production
npm run build
Run Unit Tests with Vitest
npm run test:unit
Run End-to-End Tests with Playwright
# Install browsers for the first run
npx playwright install
# When testing on CI, must build the project first
npm run build
# Runs the end-to-end tests
npm run test:e2e
# Runs the tests only on Chromium
npm run test:e2e -- --project=chromium
# Runs the tests of a specific file
npm run test:e2e -- tests/example.spec.ts
# Runs the tests in debug mode
npm run test:e2e -- --debug
Lint with ESLint
npm run lint
Icons license
We use two Twemoji SVG icons for our documentation panel, you can find them at:
src/assets/icon-important.svgsrc/assets/icon-info.svg
Twemoji SVG icons are licensed under CC-BY 4.0: https://creativecommons.org/licenses/by/4.0/. Copyright 2020 Twitter, Inc and other contributors.