-
Notifications
You must be signed in to change notification settings - Fork 21
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
[FR]: 'configure' command generates Kotlin rules #474
Comments
Thanks for starting this! Note that I get parse errors for relatively basic Kotlin files when using
Context: package ch.nexiot.gh.commander.api.commands
class FirmwareVersion(
val major: Int,
val minor: Int,
val patch: Int,
) {
val versionString get() = "$major.$minor.$patch"
}
configure:
languages:
javascript: false
go: false
kotlin: true
protobuf: true |
@kolloch despite that scary "parse error", we've seen that the BUILD files are actually updated in the desired way. Did |
Possible, I don't remember. I should try again. I think you do not resolve dependencies yet? My dabbling with this was mostly whether it makes sense to integrate my work with that. I solid parser does not make a big difference, since it will still not allow this solution to be perfect in detecting dependencies. But for now, it doesn't seem solid. Maybe that's easy to change! That would be awesome. For now, it would be easier for me to continue with a solution that I understand. |
The MVP for this is done, we can open more issues for more changes |
What is the current behavior?
Users have to write BUILD files by hand containing
kt_jvm_library
and other Kotlin rulesDescribe the feature
srcs
and first-partydeps
deps
on third-party maven packagesThe text was updated successfully, but these errors were encountered: