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

Ensuring only valid PascalCharacters #99

Merged
merged 2 commits into from Mar 19, 2020
Merged

Ensuring only valid PascalCharacters #99

merged 2 commits into from Mar 19, 2020

Conversation

@Keboo
Copy link
Member

Keboo commented Mar 13, 2020

Fixes #80

Questions: Is it acceptable to only allow upper/lower/number for naming on methods/properties/fields? Any counter examples?

Fixes #80

Questions: Is it acceptable to only allow upper/lower/number for naming on methods/properties/fields? Any counter examples?
@Keboo Keboo added this to the 0.1.6 milestone Mar 13, 2020
Setting pipeline to install .NET Core 3.1
@Keboo

This comment has been minimized.

Copy link
Member Author

Keboo commented Mar 13, 2020

Also as an update I am planning on rolling out the 0.1.16 release after this issue is resolved.

Copy link
Member

adamskt left a comment

Nice! Who knew they had a casing rules engine?

@Keboo

This comment has been minimized.

Copy link
Member Author

Keboo commented Mar 19, 2020

@adamskt that is my own code :)

@Keboo Keboo merged commit d57bfb4 into master Mar 19, 2020
2 checks passed
2 checks passed
IntelliTect.CodingStandards Build #20200313.2 succeeded
Details
WIP Ready for review
Details
@Keboo Keboo deleted the fix80 branch Mar 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

2 participants
You can’t perform that action at this time.