generated from TBD54566975/tbd-project-template
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Move codegen from Maven into the ftl
tooling.
#970
Comments
18 tasks
Open
alecthomas
changed the title
Codegen in
Move codegen from Maven into the Feb 22, 2024
ftl
toolingftl
tooling.
worstell
added a commit
that referenced
this issue
Feb 26, 2024
worstell
added a commit
that referenced
this issue
Feb 26, 2024
worstell
added a commit
that referenced
this issue
Feb 26, 2024
worstell
added a commit
that referenced
this issue
Feb 26, 2024
worstell
added a commit
that referenced
this issue
Feb 26, 2024
worstell
added a commit
that referenced
this issue
Feb 27, 2024
worstell
added a commit
that referenced
this issue
Feb 27, 2024
worstell
added a commit
that referenced
this issue
Feb 27, 2024
fixes #970 This implementation diverges from the kotlin-runtime module generator logic in that it omits `IngressHttp` or `Json` annotations in external modules. I don't think we need those for the generated external modules. Will follow with a change to remove the module generator entirely and stop releasing its JAR. --------- Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Use the same pattern as
go-runtime/compile.Build
, which uses scaffolder to generate stubs in Go. We want the same thing in Kotlin. Useinternal.ScaffoldZip()
rather than scaffolder directly, as it adds common functions.The way we get the templates into the
ftl
binary differs between development mode and production. In development we load zip files directly from disk. In a production release build we usebit
to build the zip and go:embed to embed it. See devel.go and release.go for examples.I would just shove in the entire schema as the template context, removing any modules that the target module isn't importing.
The text was updated successfully, but these errors were encountered: