clean-sapl issueshttps://gitlab.science.ru.nl/clean-and-itasks/clean-sapl/-/issues2018-07-09T10:16:58+02:00https://gitlab.science.ru.nl/clean-and-itasks/clean-sapl/-/issues/4saplcg in wrong location2018-07-09T10:16:58+02:00Bas Lijnsesaplcg in wrong locationThe `saplcg` tool is now in `Libraries` but it should be in `Tools`.The `saplcg` tool is now in `Libraries` but it should be in `Tools`.Bas LijnseBas Lijnsehttps://gitlab.science.ru.nl/clean-and-itasks/clean-sapl/-/issues/3Parser should accept input without functions2018-07-02T12:44:22+02:00Camil StapsParser should accept input without functionsFor instance, the Sapl file for StdEnv looks like:
```sapl
|| ?module? StdEnv
|| Converted Records
```
Feeding that to the parser gives `Not a function or type definition at line 6 before character 21`. It seems that the parser cou...For instance, the Sapl file for StdEnv looks like:
```sapl
|| ?module? StdEnv
|| Converted Records
```
Feeding that to the parser gives `Not a function or type definition at line 6 before character 21`. It seems that the parser could just return an empty function list.https://gitlab.science.ru.nl/clean-and-itasks/clean-sapl/-/issues/2master branch is not the master branch and should be swapped with hierarchical2018-06-12T07:57:28+02:00Mart Lubbersmaster branch is not the master branch and should be swapped with hierarchicalhttps://gitlab.science.ru.nl/clean-and-itasks/clean-sapl/-/issues/1Limitations not clearly documented2018-06-11T14:36:50+02:00Bas LijnseLimitations not clearly documentedThe conversion between clean expressions and sapl is only possible under certain conditions (sharing breaks, everything becomes hyperstrict etc). This should be documented more clearly to prevent people from accidentally using it when wh...The conversion between clean expressions and sapl is only possible under certain conditions (sharing breaks, everything becomes hyperstrict etc). This should be documented more clearly to prevent people from accidentally using it when when these conditions don't hold.