-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upgrading to 4.0.0 #48
Comments
@dhakehurst @ufobat I see the same issue, looks like type-model is not published to maven. |
hmm... I will sort it out ASAP, |
Something went wrong with the publish process to maven central. hope that works ok for you now. |
some help would really be appreciated. Is there any updated documentation? i used to do it like that, while
I assume the new startpoint is something like that:
but where does my SyntaxAnalyzer come in to that code? |
Hi.
Sorry. Lots of api changes and lack of time to document.
Check the code and tests for examples. Ie
https://github.com/dhakehurst/net.akehurst.language/blob/master/net.akehurst.language/agl-processor/src/commonMain/kotlin/agl/processor/Agl.kt
The fromStringDefault creates a default syntax analyser.
Try the more general function if you want to provide your own 'processor-parts'.
they are provided by 'configuration'.
```
val processor = Agl.processorFromString(grammarStr, Agl.configuration {
syntaxAnalyserResolver{
ProcessResultDefault(EvalDefinitionSyntaxAnalyser(), IssueHolder(LanguageProcessorPhase.ALL))
}
})
```
then the result of processing a sentence is a 'ProcessResult'.
which contains an 'asm' and a list of 'issues'.
E.g.
```
val res = processor.process<Assignment>(definition)
check(res.issues.errors.isEmpty())
val assignment = res.asm!!
```
(hope that helps).
|
I wanted to upgrad from 3.5.2 to to 4.0.0 by changing the lines in my
build.gradle.kts
file. I changed the lineAnd this error happens:
what is this type-model:
Could not find net.akehurst.language:type-model:4.0.0.
Do i have to add something more? Any advice?
The text was updated successfully, but these errors were encountered: