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

Alire.Crate.Configuration: disable style checks in generated code #1047

Merged
merged 1 commit into from
Jun 8, 2022

Conversation

Fabien-Chouteau
Copy link
Member

With the current style checks it is easy to break coding style by having
to many values in an enum for instance.

In theory we could generate better code for enums. But since users can
use their own coding style, it is impossible to be compatible with in
every situation.

So the best option is to disable all checks for this file.

With the current style checks it is easy to break coding style by having
to many values in an enum for instance.

In theory we could generate better code for enums. But since users can
use their own coding style, it is impossible to be compatible with in
every situation.

So the best option is to disable all checks for this file.
@Fabien-Chouteau Fabien-Chouteau requested a review from mosteo June 8, 2022 09:01
@mosteo mosteo merged commit 877ef22 into master Jun 8, 2022
@mosteo mosteo deleted the config_style_checks_off branch June 8, 2022 09:24
@Fabien-Chouteau
Copy link
Member Author

@mosteo something we can push to the 1.2 branch as it can be an annoying situation to face. Speaking from experience ^^

@mosteo
Copy link
Member

mosteo commented Jun 8, 2022

OK, I'll apply it and we can push out a 1.2.1

@Fabien-Chouteau
Copy link
Member Author

Not sure it's worth a .1 yet.
BTW we should also add the GNAT Studio message change.

@mosteo
Copy link
Member

mosteo commented Jun 8, 2022

Yeah, we can wait for a while so things consolidate a bit. I also had the GNAT Studio message in mind, thanks for the reminder.

mosteo pushed a commit that referenced this pull request Jun 8, 2022
)

With the current style checks it is easy to break coding style by having
to many values in an enum for instance.

In theory we could generate better code for enums. But since users can
use their own coding style, it is impossible to be compatible with in
every situation.

So the best option is to disable all checks for this file.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants