Looking for Naming Convention help

[Stuart Hemming]

We have a rule in place that requires all methof parameters to be PascalCase ...

GetContact(int ContactId) {}

But having set this up JC wants to use PascalCase names for LINQ ...

item.Checked = ContactTypesList.Any(t => t.ContactTypeId == Int32.Parse(item.Value));

Here it complains that 't' in the Any method should be 'T'.

Now, I know that this is working as designed, but is there any way I can set up a secondary rule to get it to accept pascalCase parameters for LINQ extensions?

--
Stuart

[Stuart Hemming]

Of course, in the final paragraph of my last, I meant camelCase!

[Zdravko]

Hello Stuart,

 Thanks for contacting us.
We have a story in our system for further implementation of a rule for lambda parameters, but it is not pretty clear when it will be implemented.

So far I could suggest you to set a secondary rule for the method parameters. You could go to JustCode menu -> Options -> Code Style -> choose the desired language (e.g. C#) -> Naming conventions. Then locate the Method Parameters option and set the secondary rule by clicking the Add button.
But adding a secondary rule will prevent showing warnings when a method parameter is not PascalCase.
Thank you.

Please, do not hesitate to contact us if you have any questions or need of assistance.

All the best,
Zdravko
the Telerik team

[Steven T.]

I too want to relax my convention for lambda expressions.  Has this story made the schedule yet?

[Nikolay Valchev]

Hello,

We've already introduced such an option and you will be able to use it in our next release.

If you have any other questions, please do not hesitate to write us back!

Regards,
Nikolay Valchev
Telerik