| Commit message (Collapse) | Author | Age |
|
|
|
| |
Also make sure Sonar can process TypeScript files.
|
|
|
|
|
| |
* Add NodeFunctionView for symbols that hold function-like (single
associated object for each key) relations as integer values for performance.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make sure we obey the REUSE (https://reuse.software) specification and the
origin, copyright owner, and license of all files are clearly marked.
The whole project is under the EPL-2.0, except for trivial files where copyright
is not applicable that are marked with the CC0-1.0 license. Moreover, code
included from third parties is also available under the respective license.
chore: add CONTRIBUTORS.md
List all authors and supporting organizations in accordance with the REUSE
specification.
|
|
|
|
|
|
|
| |
Also take advantage of precompiled Kotlin scripts to write build scripts in a
more straightforward manner through generated accessors.
Might increase memory usage of Gradle.
|
| |
|
| |
|
|
|
|
| |
Allows removing Eclipse-specific generated files from the source tree quickly.
|
|
|
|
|
|
|
|
|
| |
* Always write ESLint output to a file in addition to the console to make the
lintFrontend task cacheable in Gradle (according to the output file).
* Make sure frontend task inputs are declared properly for caching.
* Make sure Typescript type checking is incremental.
* Do not use @tsconfig, because both Vite and SonarScanner have problems with
extending tsconfig files from Yarn PnP modules.
|
|
|
|
|
|
| |
Make sure we get slf4j in every test source set and every application by
default. Saves configuration effort when creating a new library that tests
VIATRA or other dependencies that require log4j.
|
| |
|
|
|
|
|
|
|
| |
Improves IDE support build scripts in IntelliJ.
There is no Eclipse IDE support, but Eclipse didn't have support for Groovy
either, so there is no degradation of functionality.
|
|
|
|
|
|
|
|
|
|
| |
* Directly transform VIATRA tuples into Refinery tuples, since creating
the additional wrapper object doesn't save any memory.
* Adds static arity Tuple3 and Tuple4 implementations to be more
aligned with VIATRA internals and save memory for queries with up to
4 parameters.
* Makes sure no new objects are allocated (for varargs handling) when a
static arity tuple is hashed.
|
|\
| |
| | |
Changes for supporting partial interpretation
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* 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
|
|
|
|
|
|
| |
Sonarqube is not yet compatible with Gradle 8:
https://sonarsource.atlassian.net/browse/SONARGRADL-84
https://github.com/SonarSource/sonar-scanner-gradle/pull/146
|
|\
| |
| |
| |
| | |
graphs4value/dependabot/npm_and_yarn/http-cache-semantics-4.1.1
build(deps): bump http-cache-semantics from 4.1.0 to 4.1.1
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
Bumps [http-cache-semantics](https://github.com/kornelski/http-cache-semantics) from 4.1.0 to 4.1.1.
- [Release notes](https://github.com/kornelski/http-cache-semantics/releases)
- [Commits](https://github.com/kornelski/http-cache-semantics/compare/v4.1.0...v4.1.1)
---
updated-dependencies:
- dependency-name: http-cache-semantics
dependency-type: indirect
...
Signed-off-by: dependabot[bot] <support@github.com>
|
|
|
|
|
|
| |
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.
|