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

Rename constants to PascalCase #58

Open
2 tasks
epels opened this issue Dec 21, 2017 · 8 comments · May be fixed by #71
Open
2 tasks

Rename constants to PascalCase #58

epels opened this issue Dec 21, 2017 · 8 comments · May be fixed by #71

Comments

@epels
Copy link

epels commented Dec 21, 2017

Steps to reproduce:

  1. Read the source code

What should happen:

  1. Constants are named in PascalCase

What happens:

  1. Constants are named IN_ALL_CAPS.

See also:

https://docs.microsoft.com/en-us/dotnet/standard/design-guidelines/capitalization-conventions

Implementations

  • Core code
  • Generated code
@OGKevin OGKevin added this to the 0.12.5 milestone Dec 21, 2017
@OGKevin OGKevin self-assigned this Dec 21, 2017
@kid-cavaquinho
Copy link

@epels @OGKevin did a quick look into 'const' keyword in the source and could not find any that was not in pascal case. Did I missed something or is this issue closed?

Thanks!

@OGKevin
Copy link
Contributor

OGKevin commented Dec 27, 2017

@AnTao I dont quite understand ?

Currently all constants are in CAPS, which is not correct according to the style guide in the OP. So the source code must be refactored to rename the constants in PascalCase as the style guide says!

@kid-cavaquinho
Copy link

@OGKevin my bad, you are right! 👍

@OGKevin
Copy link
Contributor

OGKevin commented Dec 27, 2017 via email

@kid-cavaquinho
Copy link

Thanks for the input @OGKevin , closed the other PR's cause they did not followed the naming conventions. Hopefully in the next days I will look further into the codebase 👍

@kid-cavaquinho kid-cavaquinho linked a pull request Dec 27, 2017 that will close this issue
1 task
@OGKevin OGKevin modified the milestones: 0.12.5, 0.13.0 Dec 28, 2017
@OGKevin
Copy link
Contributor

OGKevin commented Dec 28, 2017

Due to this introducing a lot of breaking change, this will be moved to 0.13.0 release instead of 0.12.5`

@OGKevin
Copy link
Contributor

OGKevin commented Dec 28, 2017

@AnTao We can still finish up the PR tho!

@OGKevin
Copy link
Contributor

OGKevin commented Dec 28, 2017

@AnTao I think the constants in the non generated files are almost done 👏 🎊 👍.

The ones in the generated folder, ill take care of them once 0.13.0 is near as this requires change in the generator and will introduce breaking change. With this being said, lets keep this on hold for now and finish up the 0.12.5 milestone.

@OGKevin OGKevin modified the milestones: 0.13.0, 0.13.5 Mar 27, 2018
@OGKevin OGKevin modified the milestones: 1.0.0, 1.1.0 Jul 24, 2018
@angelomelonas angelomelonas removed this from the 1.1.0 milestone Sep 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment