801cc7b37d
Fixes #8871 The issue was caused by invalid port registration. Because of the existing context switch expression (which is not visible in GUI), the port incorrectly considered itself to belong to another node. This happened because the port was only aware of the visible part of the node’s AST and considered it the whole node. There are two fixes in this PR. Either of them fixes the issue, and they are both implemented for robustness: 1. We provide `nodeId` information to the widget tree, so it no longer assumes the node ID from AST. 2. The order of checks in `getPortNodeId` is swapped. Now we first search by AST, only then try to look up the port. It makes sense to me because the AST is a single root of truth, and we should only rely on registered ports if AST does not exist (which happens for unconnected ports). |
||
---|---|---|
.. | ||
.vscode | ||
e2e | ||
mock | ||
parser-codegen | ||
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 | ||
node.env.d.ts | ||
package.json | ||
playwright.config.ts | ||
README.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 | ||
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 Extensions
from VSCode's command palette - Find
TypeScript and JavaScript Language Features
, right click and selectDisable (Workspace)
- Run
- Reload the VSCode window by running
Developer: Reload Window
from the command palette.
Customize configuration
See Vite Configuration Reference.
Project Setup
npm 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.svg
src/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.