relational-rags issueshttps://git-st.inf.tu-dresden.de/jastadd/relational-rags/-/issues2022-07-27T13:07:44+02:00https://git-st.inf.tu-dresden.de/jastadd/relational-rags/-/issues/34Array types not supported2022-07-27T13:07:44+02:00René SchöneArray types not supportedsee https://git-st.inf.tu-dresden.de/jastadd/relast-preprocessor/-/issues/12see https://git-st.inf.tu-dresden.de/jastadd/relast-preprocessor/-/issues/12https://git-st.inf.tu-dresden.de/jastadd/relational-rags/-/issues/31Resolving of References in NTAs2022-02-11T09:58:14+01:00Johannes MeyResolving of References in NTAs## Problem
Unresolved references in NTAs are not resolved when calling `treeResolveAll()`, because this method traverses using the `getChild()` method.
## Discussion
For NTAs specified in the grammar with `/SomeNTA/`, this can be solv...## Problem
Unresolved references in NTAs are not resolved when calling `treeResolveAll()`, because this method traverses using the `getChild()` method.
## Discussion
For NTAs specified in the grammar with `/SomeNTA/`, this can be solved by generating specific `treeResolveAll()` methods for the nonterminals containing such NTAs.
For NTAs specified in an aspect, this is hard to solve, because we don't know about these NTAs at all in the relast preprocessor.
However, this points to another problem. While `getChild()` is marked as `low-level`, it is still used in some cases. Thus, resolving should be triggered there instead of in the high-level getters.
Finally, since @johannes.mey is preparing a complete overhaul of the resolution mechanism with the goal of not having *any* resolver logic in the final generated classes, all of this discussion might be obsolete.Johannes MeyJohannes Meyhttps://git-st.inf.tu-dresden.de/jastadd/relational-rags/-/issues/29Reordering of children does not work2023-03-06T13:33:15+01:00René SchöneReordering of children does not workGiven the following grammar, ...
```
Nameable ::= <Name> ;
A : Nameable ::= B MyC:C ;
SubA : A ::= MyC:C B ;
B;
C;
```
... the following (wrong) constructor is being generated:
```
public SubA.SubA(String Name, B B, C MyC, C MyC, B B)...Given the following grammar, ...
```
Nameable ::= <Name> ;
A : Nameable ::= B MyC:C ;
SubA : A ::= MyC:C B ;
B;
C;
```
... the following (wrong) constructor is being generated:
```
public SubA.SubA(String Name, B B, C MyC, C MyC, B B)
```
The problem is located in the attribute `componentsTransitive` in `backend/Analysis.jrag`https://git-st.inf.tu-dresden.de/jastadd/relational-rags/-/issues/26Creation of jar in CI fails2023-03-06T13:36:59+01:00René SchöneCreation of jar in CI failsLast words of the job `jar` are always
```
Uploading artifacts...
WARNING: /builds/jastadd/*/build/libs/*relast*.jar: no matching files
ERROR: No files to upload
Job succeeded
```Last words of the job `jar` are always
```
Uploading artifacts...
WARNING: /builds/jastadd/*/build/libs/*relast*.jar: no matching files
ERROR: No files to upload
Job succeeded
```https://git-st.inf.tu-dresden.de/jastadd/relational-rags/-/issues/17Incomplete deserialization of inherited children and relations2020-01-10T14:06:00+01:00Johannes MeyIncomplete deserialization of inherited children and relationsInherited children are not deserialized if not the highest deserialization method in the class hierarchy is used. The intended reuse works in the Train case, but not in general. Also, the tests should be extended!Inherited children are not deserialized if not the highest deserialization method in the class hierarchy is used. The intended reuse works in the Train case, but not in general. Also, the tests should be extended!Johannes MeyJohannes Mey