| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
Imporve font rendering on Windows by making the JetBrains Mono font
slightly bolder.
|
| |
|
| |
|
|
|
|
|
| |
Might need manual intervention in browsers, e.g.
https://docs.microsoft.com/en-us/microsoft-edge/progressive-web-apps-chromium/how-to/window-controls-overlay#enable-the-window-controls-overlay-api-in-microsoft-edge
|
| |
|
|
|
|
|
|
| |
Optimize first page loading time.
We only include variable and woff2 fonts, as they are widely supported.
|
|
|
|
|
| |
Gutters are aria-hidden, so no accessibility attributes should point at
them.
|
|
|
|
|
| |
If the application is run in both production and development mode on the
same domain, make sure to clean up the production service worker.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Also improves editor styling (to enable panel styling).
|
|
|
|
| |
Also bumps frontend dependencies.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Also overhaulds the building and linting for frontend assets.
|
|
|
|
| |
This was left unchanged after refactoring the operators in the language.
|
| |
|
| |
|
|
|
|
| |
Also change refinement operator based on feedback from colleagues
|
| |
|
|
|
|
|
|
| |
* Remove the direct keyword because it can be inferred
* Use may/must/current instead of value literals
* Transformation rule changes
|
| |
|
|
|
|
|
|
| |
* Move all utilities for language-model to language, since they do not
make sense on their own
* Convert xtend code into java
|
| |
|
|
|
|
| |
See https://github.com/gradle/gradle/issues/898
|
| |
|
| |
|
| |
|
|\
| |
| | |
Restructure project
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
This allows us to simplify the webpack configuration and the gradle
build scripts.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Also requires yarn 3.2.0-rc.5 due to
https://github.com/yarnpkg/berry/issues/3722
|
| |
| |
| |
| | |
See https://yarnpkg.com/getting-started/editor-sdks/#emacs for more info
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Check for the presence of the secret directly (instead of whether we're
in a pull request) for a more robust CI.
We check the secret according to
https://github.community/t/how-can-i-test-if-secrets-are-available-in-an-action/17911
To determine the clone depth (deep for sonar analysis, shallow
otherwise) we use the "fake ternary" method from
https://github.community/t/do-expressions-support-ternary-operators-to-change-their-returned-value/18114
|
| |
| |
| |
| |
| | |
File was accidentally extrated from language.jar and added to the
repository.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The root project (worktree) must have a valid package.json,
.yarnrc.yaml, and have the gradle precompiled script plugin
refinery-frontend-worktree applied to it.
All frontend modules (workspaces) must have a valid package.json, be
referenced in the worktree project.json, and be a valid gradle
subproject with the gradle precompiled script plugin
refinery-frontend-workspace applied to it.
To reduce unnecessary downloads, we do the following workarounds:
* The node version is pinned in gradle.properties and the installed node
version is stored in .node/frontend.properties. A new node version is
only downloaded if it differs from the installed one (or none is
installed). This improves on the default gradle behavior, which would
download a new node version if the classpath of the installNode task
was changed.
* The yarn classic version is pinned in gradle.properties and the
installed yarn classic version is stored in .node/frontend.properties.
This improves on the default gradle behavior, which would reinstall
the yarn npm package at every build.
* We disable the enableYarnBerry task, since a yarn berry version is
already committed into the repository at .yarn/versions as it is
recommended in http://yarnpkg.com/getting-started/qa/
* We use yarn set version --only-if-needed in the installYarn task.
* The installFrontend task takes package.json and yarn.lock as inputs
and produces .pnp.cjs and .pnp.loader.mjs as outputs. Whether this
task is up-to-date can be checked by gradle quickly, since it doesn't
have to traverse the node_module folder due to pnp resoltion:
https://yarnpkg.com/features/pnp/
All workspaces have the installNode, installYarnGlobally, installYarn
and installFrontend tasks disabled. However, these tasks depend on the
task with the same name in the worktree project, so installation is
still triggered globally. Moreover, the installFrontend task in the
worktree has the package.json of the workspaces as inputs, so
reinstallation is triggered when the workspace package.json changes.
|
| |
| |
| |
| |
| | |
It is not compatible with eslint 8 yet:
https://github.com/SonarSource/eslint-plugin-sonarjs/issues/286
|