-
Notifications
You must be signed in to change notification settings - Fork 14
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
Feature/mip 399 #16
Feature/mip 399 #16
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just make sure you run codeNarc and code Inspector on this as well
|
||
class FlowSubflowNamingRule extends Rule { | ||
|
||
enum CaseFormat { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would pull this logic out into a StringUtil or StringParser(?) I know Adam doesn't like naming classes 'Util'....
We would want to be able to check any string, against a format... so that it can be reused in many rules...
Then we can write some tests that just parse strings, and you wouldn't need so many config files...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done.
@kkingavio take a look again, made changes as suggested. |
|
||
private static final String NAMING_APP = 'FlowSubflowNaming' | ||
|
||
private static final String CAMEL_CASE_FILE = 'camelCase.xml' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Limit to 1 file that contains a flow for each naming case... and check that the correct flow passes in each of the different naming scenarios.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done.
Flow subflow naming convention rule -> camelCase, PascalCase, snake_case, and kebab-base