Skip to content
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

Merged
merged 4 commits into from
Jul 9, 2020
Merged

Feature/mip 399 #16

merged 4 commits into from
Jul 9, 2020

Conversation

thedevnisarg
Copy link
Contributor

Flow subflow naming convention rule -> camelCase, PascalCase, snake_case, and kebab-base

Copy link
Contributor

@kkingavio kkingavio left a 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 {
Copy link
Contributor

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...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.

@thedevnisarg thedevnisarg requested a review from kkingavio July 9, 2020 15:24
@thedevnisarg
Copy link
Contributor Author

@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'
Copy link
Contributor

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done.

@thedevnisarg thedevnisarg merged commit 8b72238 into develop Jul 9, 2020
@thedevnisarg thedevnisarg deleted the feature/MIP-399 branch July 9, 2020 18:19
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