Skip to content

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

Merged
mosteo merged 1 commit into
masterfrom
config_style_checks_off
Jun 8, 2022
Merged

Alire.Crate.Configuration: disable style checks in generated code#1047
mosteo merged 1 commit into
masterfrom
config_style_checks_off

Conversation

@Fabien-Chouteau

Copy link
Copy Markdown
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
Copy Markdown
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

mosteo commented Jun 8, 2022

Copy link
Copy Markdown
Member

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

@Fabien-Chouteau

Copy link
Copy Markdown
Member Author

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

@mosteo

mosteo commented Jun 8, 2022

Copy link
Copy Markdown
Member

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