Skip to content
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

Decide on how to handle generated code used to access KeyVault and the Lab API #1175

Open
shoatman opened this issue Apr 26, 2018 · 0 comments
Assignees
Labels
Enhancement This is a feature request to add functionality that is not currently supported Internal Issue created by a project contributor Issue Triage The engineering team has looked into the issue, understood the issue, labelled/classified the issue

Comments

@shoatman
Copy link
Contributor

Currently the generated code is included in the project as source. Should we instead include references to a jar? How do we document the code generation process so that others in the team can update the generated code easily?

@iambmelt iambmelt added Enhancement This is a feature request to add functionality that is not currently supported Internal Issue created by a project contributor Issue Triage The engineering team has looked into the issue, understood the issue, labelled/classified the issue labels Dec 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement This is a feature request to add functionality that is not currently supported Internal Issue created by a project contributor Issue Triage The engineering team has looked into the issue, understood the issue, labelled/classified the issue
Projects
None yet
Development

No branches or pull requests

2 participants