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

Add a guideline for variable naming convention #1003

Closed
GauravGusain98 opened this issue Sep 17, 2021 · 2 comments
Closed

Add a guideline for variable naming convention #1003

GauravGusain98 opened this issue Sep 17, 2021 · 2 comments
Assignees
Labels
documentation Targets documentation corrections and upgrades Points: 1 Good for beginners. Tasks that require not more than 4 hours to finish. status : ready to test Items that are ready for testing

Comments

@GauravGusain98
Copy link
Contributor

Describe the task
Add a guideline for the naming conventions followed in PHP, blade, js, css and vue file

Expected behavior
Add a documentation file.

References
JS:
className - snake-case
idName - camelCase
PHP:
variable name - camelCase
function name - camelCase
class name - TitleCase
Blade:
variable name - camelCase
className - snake-case
idName - camelCase

@GauravGusain98 GauravGusain98 added the documentation Targets documentation corrections and upgrades label Sep 17, 2021
@gautam071
Copy link
Contributor

gautam071 commented Sep 17, 2021

@GauravGusain98 Can you link the branch name documentation here it will be helpful
OR examples for the branch name here.

@srivastava-jyoti srivastava-jyoti added this to the Oct-30 to Nov-5 milestone Oct 30, 2021
@srivastava-jyoti srivastava-jyoti added the Points: 1 Good for beginners. Tasks that require not more than 4 hours to finish. label Oct 30, 2021
@Ayush8923 Ayush8923 self-assigned this Oct 30, 2021
@GauravGusain98 GauravGusain98 added the status : ready to test Items that are ready for testing label Nov 30, 2021
@srivastava-jyoti
Copy link
Contributor

Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Targets documentation corrections and upgrades Points: 1 Good for beginners. Tasks that require not more than 4 hours to finish. status : ready to test Items that are ready for testing
Projects
None yet
Development

No branches or pull requests

5 participants