aws
feat(kotlin): add Kotlin/JVM target to pacmak
Add initial support for the Kotlin programming language in the pacmak generator.
Currently, the Kotlin generator can produce Java-like stubs for Kotlin/JVM. It reuses the existing Java runtime library.
Current plans:
- [ ] Make stubs a bit more Kotlin-friendly;
- [ ] Generate
data-like constructors with named/optional parameters;
- [ ] Generate
- [ ] Add Kotlin/JavaScript generation mode.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
The title of this Pull Request does not conform with [Conventional Commits] guidelines. It will need to be adjusted before the PR can be merged. [Conventional Commits]: https://www.conventionalcommits.org
![mergify[bot] avatar](https://avatars.githubusercontent.com/in/10562?v=4 "Published by a pub.dev verified publisher"){kind=small}
AWS CodeBuild CI Report
- Result: FAILED
- Build Logs (available for 30 days)
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository
The title of this Pull Request does not conform with [Conventional Commits] guidelines. It will need to be adjusted before the PR can be merged. [Conventional Commits]: https://www.conventionalcommits.org
The title of this Pull Request does not conform with [Conventional Commits] guidelines. It will need to be adjusted before the PR can be merged. [Conventional Commits]: https://www.conventionalcommits.org
The title of this Pull Request does not conform with [Conventional Commits] guidelines. It will need to be adjusted before the PR can be merged. [Conventional Commits]: https://www.conventionalcommits.org
The title of this Pull Request does not conform with [Conventional Commits] guidelines. It will need to be adjusted before the PR can be merged. [Conventional Commits]: https://www.conventionalcommits.org
The title of this Pull Request does not conform with [Conventional Commits] guidelines. It will need to be adjusted before the PR can be merged. [Conventional Commits]: https://www.conventionalcommits.org
AWS CodeBuild CI Report
- Result: FAILED
- Build Logs (available for 30 days)
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository
AWS CodeBuild CI Report
- Result: FAILED
- Build Logs (available for 30 days)
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository
AWS CodeBuild CI Report
- Result: FAILED
- Build Logs (available for 30 days)
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository
AWS CodeBuild CI Report
- Result: FAILED
- Build Logs (available for 30 days)
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository
I think it would make sense to make all Props classes data classes, especially due to the copy() function it would make available. I can see a use for making a Props instance that has a lot of common properties, then using copy() to make more specific instances for use in actual resource definitions.
(Sorry, I don't know this code-generation code enough well enough to see whether this has already been done or not, or against what code this comment belongs.)
This had been closed in error as I renamed the master branch over to main. Sorry about that!
AWS CodeBuild CI Report
- CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
- Commit ID: 601c9edef8295605d7c8fc6129443aa3743866c8
- Result: FAILED
- Build Logs (available for 30 days)
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository
