Fixed clang configuration file

[Hadatko]

• reformatted code.

Pull request

Choose Correct

• bug
• feature

Describe the pull request

I noticed that some clang-format config values were changed for version we have. So i adapt them and added one more which was not available.

To Reproduce

Expected behavior

Screenshots

Desktop (please complete the following information):

• OS:
• eRPC Version:

Steps you didn't forgot to do

• I checked if other PR isn't solving this issue.
• I read Contribution details and did appropriate actions.
• PR code is tested.
• PR code is formatted.
• Allow edits from maintainers pull request option is set (recommended).

Additional context

[MichalPrincNXP]

Hi Dusan, thank you. Would it be possible to move to LLVM16 to be aligned with MCUXpressoSDK formatting?

[Hadatko]

Hi @MichalPrincNXP, does last commit matched your preference?

[isolansky]

Strings should not have wrapping with quotes.

The following one is questionable:

BreakInheritanceList: "BeforeComma"

I propose to use any from rest of two values

[Hadatko]

Hi @isolansky , i don't understand your first line. If we want to be consistent we can take a look how it looks like in initializing contructor. Newline is before comma. Then we need change both.

But personally this is cleaner as comma is aligned with ":"

[isolansky]

From my understanding, goal is to have code, easily mergable with other projects (under MCUX) or using MSDK in other way.
From my experiences I always got commas at the line end from OSS either from in-company code. So thus asking if there is any other kind of strong motivation for this. If it is just personal feeling, or some big related project.

[Hadatko]

I think you are mixing apples and pears ;) We are trying to align C++ code style with NXP code style. But NXP doesn't have C++ code style (afaik) so we should discuss what is best for C++ specific cases. My suggestion looks like block so easier to read.

Anyway as mentioned before. If we do your requested change it would lead to inconsistency with constructor declaration. So we need keep current settings or change both.

(it looks this type of inconsistency is present in webkit. Do you still like Mozilla? They are using my proposed change :D)

[Hadatko]

@MichalPrincNXP @isolansky Your requests are placed. I noticed that clang check was not call on PR change so i added this option and moved excluded files list to its own file so we can have one source of excluded files for two different usage of clang format.

[isolansky]

Thank you, also for pointed out that include sorting based on grouping. This will be subject of future consideration.

[Hadatko]

@isolansky That sounds great. Also in that case you would have to use:
IncludeBlocks: Preserve

[Hadatko]

FYI: @MichalPrincNXP this should be ready too.

[MichalPrincNXP]

thank you, Dusan