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

Config Doc - Commit somewhere the model and the output #42447

Open
gsmet opened this issue Aug 9, 2024 · 1 comment
Open

Config Doc - Commit somewhere the model and the output #42447

gsmet opened this issue Aug 9, 2024 · 1 comment
Assignees

Comments

@gsmet
Copy link
Member

gsmet commented Aug 9, 2024

When working on the extension annotation processor, it can be hard to check that a change doesn't create unwanted side effects.
Or to easily spot that a change does what is intended.

I think we should commit somewhere the generated model and the output.
Or maybe have a way to centralize them easily and compare.

In any case, I don't think we should commit it to the main repo or it will get out of hands.

/cc @cescoffier and @radcortez for discussion when they're back.

@gsmet gsmet self-assigned this Aug 9, 2024
@quarkus-bot
Copy link

quarkus-bot bot commented Aug 9, 2024

/cc @radcortez (config)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant