You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
See #44.
"The current loadAssets workaround will result into a ksp error if
only tasks like kspDebug are executed. The reason is that the build
folder does not have the information from the assets folder (from
the tests or apps build command) yet."
This can lead to an unexpected behavior for multiple clean builds like: ./gradlew clean test
Describe the solution you'd like
Since KSP has a limited access to assets and resources provided by the app developer this problem has to be solved on gradle level.
Create a plugin which has to be integrated by the user when using our KSP library. The plugin should copy every compatible .yaml file (in the future also .json etc.) to the build directory so that the KSP processor has always access to it.
Update documentation
./gradlew clean kspDebugKotlin should generate all models
Describe alternatives you've considered
Let the user copy paste Gradle code and document it (Not as convenient)
The text was updated successfully, but these errors were encountered:
The plugin is a composite project which means a higher separation to
the other modules and common buildSrc plugins can't be used here. So
plugins like publish / version had to be copied. The publish script
had to be adapted for publishing a plugin
closeeclipse-kuksa#45
Signed-Off-By: Mark Hüsers <mark.huesers@etas.com>
Is your feature request related to a problem? Please describe.
See #44.
"The current loadAssets workaround will result into a ksp error if
only tasks like kspDebug are executed. The reason is that the build
folder does not have the information from the assets folder (from
the tests or apps build command) yet."
This can lead to an unexpected behavior for multiple clean builds like:
./gradlew clean test
Describe the solution you'd like
Since KSP has a limited access to assets and resources provided by the app developer this problem has to be solved on gradle level.
Describe alternatives you've considered
The text was updated successfully, but these errors were encountered: