-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add VSS Symbol Processing processor #11
Conversation
Signed-Off-By: Mark Hüsers <mark.huesers@etas.com>
Instead of using the generic interface VSSSpeciaction, all classes are now references to the concrete class type.
Duplicated names like "Middle" with different vssPaths should be added as nested classes.
Some description have a "," so the parsing would be incorrect.
Consists of common models used inside the SDK + Processor
- Some cleanup + renaming
No logical changes were made besides adapting the code to the new interface.
Had to force push the author so it matches my eclipse account e-mail. |
app/src/main/kotlin/org/eclipse/kuksa/testapp/databroker/DataBrokerEngine.kt
Outdated
Show resolved
Hide resolved
kuksa-sdk/src/main/kotlin/org/eclipse/kuksa/DataBrokerConnection.kt
Outdated
Show resolved
Hide resolved
app/src/main/java/org/eclipse/kuksa/testapp/databroker/JavaDataBrokerEngine.java
Outdated
Show resolved
Hide resolved
vss-core/src/main/java/org/eclipse/kuksa/vsscore/model/VssSpecification.kt
Show resolved
Hide resolved
vss-processor/src/main/kotlin/org/eclipse/kuksa/vssprocessor/YamlDefinitionParser.kt
Outdated
Show resolved
Hide resolved
app/src/main/kotlin/org/eclipse/kuksa/testapp/databroker/viewmodel/ConnectionViewModel.kt
Outdated
Show resolved
Hide resolved
app/src/main/kotlin/org/eclipse/kuksa/testapp/databroker/viewmodel/ConnectionViewModel.kt
Outdated
Show resolved
Hide resolved
app/src/main/kotlin/org/eclipse/kuksa/testapp/databroker/viewmodel/ConnectionViewModel.kt
Outdated
Show resolved
Hide resolved
kuksa-sdk/src/main/kotlin/org/eclipse/kuksa/DataBrokerConnection.kt
Outdated
Show resolved
Hide resolved
kuksa-sdk/src/main/kotlin/org/eclipse/kuksa/DataBrokerConnection.kt
Outdated
Show resolved
Hide resolved
kuksa-sdk/src/main/kotlin/org/eclipse/kuksa/DataBrokerConnection.kt
Outdated
Show resolved
Hide resolved
kuksa-sdk/src/main/kotlin/org/eclipse/kuksa/DataBrokerConnection.kt
Outdated
Show resolved
Hide resolved
...ocessor/src/test/kotlin/org/eclipse/kuksa/vssprocessor/spec/VssSpecificationSpecModelTest.kt
Show resolved
Hide resolved
CI fails due to missing license headers in 2 files:
|
# Conflicts: # build.gradle.kts # kuksa-sdk/build.gradle.kts
# Conflicts: # app/src/main/kotlin/org/eclipse/kuksa/testapp/KuksaDataBrokerActivity.kt # kuksa-sdk/src/main/kotlin/org/eclipse/kuksa/DataBrokerConnection.kt
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Functional Test looked good (fetch, subscribe, minify, consumer-proguard-rules).
I still expect some follow-up findings or changes during the integration into the Demo app, but I can't anticipate them yet.
LGTM
please check |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. What I did:
- build project ran App with two different yaml files
- build project with one yaml file that has some errors like not a real datatype and its not working -> good
check conflciting files please :) |
# Conflicts: # app/build.gradle.kts # app/src/main/java/org/eclipse/kuksa/testapp/databroker/JavaDataBrokerEngine.java # app/src/main/kotlin/org/eclipse/kuksa/testapp/KuksaDataBrokerActivity.kt # app/src/main/kotlin/org/eclipse/kuksa/testapp/databroker/DataBrokerEngine.kt # app/src/main/kotlin/org/eclipse/kuksa/testapp/databroker/KotlinDataBrokerEngine.kt # app/src/main/kotlin/org/eclipse/kuksa/testapp/databroker/view/DataBrokerView.kt # app/src/main/kotlin/org/eclipse/kuksa/testapp/databroker/viewmodel/ConnectionViewModel.kt # app/src/main/kotlin/org/eclipse/kuksa/testapp/extension/UriExtension.kt # gradle/libs.versions.toml # kuksa-sdk/build.gradle.kts # kuksa-sdk/consumer-rules.pro # kuksa-sdk/src/test/kotlin/org/eclipse/kuksa/DataBrokerConnectionTest.kt # kuksa-sdk/src/test/kotlin/org/eclipse/kuksa/DataBrokerConnectorSecureTest.kt # kuksa-sdk/src/test/kotlin/org/eclipse/kuksa/DataBrokerConnectorTest.kt # kuksa-sdk/src/test/kotlin/org/eclipse/kuksa/databroker/DataBrokerConfig.kt # kuksa-sdk/src/test/kotlin/org/eclipse/kuksa/databroker/DataBrokerConnectorProvider.kt # kuksa-sdk/src/test/kotlin/org/eclipse/kuksa/kotest/KotestProjectConfig.kt # kuksa-sdk/src/test/kotlin/org/eclipse/kuksa/kotest/Tag.kt # kuksa-sdk/src/test/kotlin/org/eclipse/kuksa/pattern/listener/MultiListenerTest.kt # kuksa-sdk/src/test/kotlin/org/eclipse/kuksa/test/databroker/DataBrokerConfig.kt # kuksa-sdk/src/test/kotlin/org/eclipse/kuksa/test/databroker/DataBrokerConnectorProvider.kt # kuksa-sdk/src/test/kotlin/test/databroker/DataBrokerConfig.kt # kuksa-sdk/src/test/kotlin/test/databroker/DataBrokerConnectorProvider.kt # kuksa-sdk/src/test/kotlin/test/kotest/KotestProjectConfig.kt # kuksa-sdk/src/test/kotlin/test/kotest/Tag.kt # settings.gradle.kts # test/src/main/java/org/eclipse/kuksa/test/kotest/KotestProjectConfig.kt # test/src/main/java/org/eclipse/kuksa/test/kotest/Tag.kt
@lukasmittag @wba2hi Merged main into feature branch and fixed all conflicts. Pls have a quick look :) |
LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Closes #4
An input specification file (for now only .yaml is supported) can now be injected via an annotation. Like this:
@VssDefinition("vss_rel_4.0.yaml")
For example from here: https://github.com/COVESA/vehicle_signal_specification/releases/tag/v4.0
The new KSP module will now generate fitting Kotlin data classes which can be used in combination with the SDK. This will simplify the back and forth parsing of the manual approach (vssPath + value) tremendously. See the API doc for the new methods inside the DataBrokerConnection for detailed information.
TODO: Unit tests will follow. After discussions with the reviewers we wanted to start the review already because it's a big feature.
Potential features for the future: