-
Notifications
You must be signed in to change notification settings - Fork 168
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 Coding Style Guides part #1
Comments
Is this the part you mentioned in CONTRIBUTING?
|
I thought about a Regex Coding Style Guides. Is there a guide of best practices and a kind of norm to write a regex? |
Looks like it's Regular Expression Style Guides. Not the code one. I didn't see any best practices for Regular Expression so far, only lots of tutorial and document. Perhaps the style might be like this |
style-guide, code and naming conventions by the organization Regexps. |
@aloisdg we agreed there, it not make much sense to for some strict things. We will just do some scaffolders, project generators and boilerplates to allow faster adoption and development. We just trying to follow only some naming convention and always return function that returns the regex. And that's really pretty enough when I rethink it. And want to point it out again, the organization isn't only for Javascript. When I created the organization and ping first mentions of some persons I wanted and still wants to collect all regular expressions in one place and all around them - tools, services, websites, wikis, discussions. Im very busy know, but to the end of the month I will start moving the project in some way. It also needs shares, tweets, website, wikis and even twitter profile. I will add this list to the our WIKI. Thanks for the reference. Next time can ping me by username. :) |
ping @tunnckoCore Thanks for your comment 👍 |
I join @huei90 to thank you, @tunnckoCore , for the comment. |
No description provided.
The text was updated successfully, but these errors were encountered: