| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 4.2.1 to 4.2.3.
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v4.2.3/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v4.2.3/packages/vite)
---
updated-dependencies:
- dependency-name: vite
dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Implement data terms for computations in queries.
* Function-like queries with computed results.
* Improved query evaluation, including positive and negative diagonal
cosntraints.
* Preliminary local search support.
* Changes to the DNF representation for count and aggregation support.
feat: terms wip
feat: query terms wip
feat: query evaluation, diagonal constraints, local search wip
fix reasoning compilation wip
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Accessing VIATRA result sets through IQueryResultProvider requires a lot
of indirection, allocations, and locking.
We use reflection instead to have direct access to the underlying
Indexer instead.
Unfortunately, projection to arbitrary tuple masks (with wildcard
entries in a tuple) is completely broken in VIATRA when RETE update
propagation is delayed. While a new, ad-hoc projection indexer gets
added to the RETE net immediately, it is not populated with the
projection results until updates are flushed in the query engine.
Therefore, when encountering an ad-hoc projection for the first time,
the projection results will always be empty (thus usually out of date).
While declaring the desired projections ahead of time would be a
possible solution, for now, we completely remove ad-hoc projection
support. If projections are needed on the ModelQuery level, we should
create an API for declaring projections for each registered Dnf.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Allows more complicated dependency hiearchies (e.g., use
store-query-viatra for testing store-partial) and better separation of
test fixtures.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Makes the intent of the code clearer by explicitly overriding equals and
hashCode for by-reference comparison. Also fixes Sonar warning.
|
|
|
|
|
| |
Bug was pointed out by Sonar:
https://sonarcloud.io/project/issues?open=AYYT39yQKbLNgAqL21xC&id=graphs4value_refinery
|
|
|
|
|
|
| |
Make sure to generate TypeScript type definitions before ESLint is
invoked. Missing type definitions for tsconfig references generate lont
errors.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Use PVisibility.EMBEDDED helper patterns to avoid superfluous production
nodes in the Rete net.
|
|
|
|
| |
Use Adapters to simplify API usage.
|
| |
|
|
|
|
|
| |
Make sure the CodeMirror DOM is fully ready before inserting a spacer
element for overscroll behavior.
|
| |
|
|
|
|
|
|
|
| |
The Java hashCode and equals API is inappropriate here, because an
AnyVersionedMap is mutable. Added new methods to hash and compare
AnyVersionedMap instances by their contents and marked the built-in Java
methods as deprecated.
|
| |
|
|
|
|
|
|
| |
Prefers sealed non-generic interfaces over wildcard types to avoid
confusion about method return types, especially in collections
(see SonarQube rule java:S1452).
|
|
|
|
|
|
|
| |
Support for typescript@4.9.4 available in yarn 4.0.0-rc.33 according to
https://github.com/yarnpkg/berry/pull/5127#issuecomment-1345664949
Also updates other frontend dependencies.
|
|
|
|
|
| |
Also refactor virtual thread ExecutorService handling and integration
tests.
|
|
|
|
|
| |
Also introduces tsconfig.shared.json to keep track of source files used
both and build time and in the browser.
|
|
|
|
|
| |
Improve time to a usable editor by loading the xtext client lazily.
The already existing delay to connect masks the delay of loading.
|
|
|
|
|
|
| |
vite-plugin-inject-preload and vite-plugin-pwa generate peer dependency
warnings, because they still require vite 3, but this does not lead to
any incorrect behavior in practice.
|
|
|
|
| |
We will have to implement counting in DNF queries in another way.
|
| |
|
| |
|
|
|
|
| |
Thanks @marci543
|
| |
|
| |
|
|
|
|
| |
Mimics the polular behavior from Codium.
|
| |
|
|
|
|
| |
Also test with virtual threads in we are using them in production.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Use Java 19 and Jetty 12 to take advantage of Project Loom preview
features to reduce CPU usage due to XtextWebDocumentAccess thread pools.
|