History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: RSRP-28465
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Eugene Pasynkov
Reporter: Andrew Serebryansky
Votes: 3
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
ReSharper

Enforce naming conventions

Created: 05 Sep 06 20:02   Updated: 21 May 07 19:27
Component/s: Code Analysis
Fix Version/s: Mirabilie Futurum
Security Level: Everybody (All jira users)

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Issue Links:
Duplicate
 
This issue is duplicated by:
RSRP-33182 Программирование по Guidliness Normal Closed

Build: 259


 Description  « Hide
Ideally we should be able to define our naming conventions (camel casing for parameters e.t.c.), and set the level of the highlighting (e.g. Error, Warning)

The formatting would be handy to quickly refactor the errors/warnings so that we can comply with the group standards once set.



 All   Comments   Work Log   Change History      Sort Order:
Ilya Ryzhenkov - 18 Mar 07 21:51
When (if) naming system is ready, add suggestions about wrong naming and appropriate QF to fix naming.