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

Naming conventions not followed #32

Open
VWoeltjen opened this issue Dec 18, 2017 · 0 comments
Open

Naming conventions not followed #32

VWoeltjen opened this issue Dec 18, 2017 · 0 comments

Comments

@VWoeltjen
Copy link

Sources in example/notebook do not follow naming conventions from the contributing guide; specifically:

  • Follow “Java-like” naming conventions. These includes:
  • Classes should use camel case, first letter capitalized
    (e.g. SomeClassName).
  • Methods, variables, fields, and function names should use camel case,
    first letter lower-case (e.g. someVariableName).
  • Constants (variables or fields which are meant to be declared and
    initialized statically, and never changed) should use only capital
    letters, with underscores between words (e.g. SOME_CONSTANT).
  • File names should be the name of the exported class, plus a .js extension
    (e.g. SomeClassName.js).
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

No branches or pull requests

1 participant