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 Coding Style Guides part #1

Closed
aloisdg opened this issue May 21, 2015 · 7 comments
Closed

Add a Coding Style Guides part #1

aloisdg opened this issue May 21, 2015 · 7 comments

Comments

@aloisdg
Copy link
Owner

aloisdg commented May 21, 2015

No description provided.

@hueitan
Copy link
Collaborator

hueitan commented Jul 2, 2015

Is this the part you mentioned in CONTRIBUTING?

  • Use the following format: LIBRARY - DESCRIPTION

@aloisdg
Copy link
Owner Author

aloisdg commented Jul 2, 2015

I thought about a Regex Coding Style Guides. Is there a guide of best practices and a kind of norm to write a regex?

@hueitan
Copy link
Collaborator

hueitan commented Jul 2, 2015

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
use \d instead of [0-9]
some kind like that?

@aloisdg
Copy link
Owner Author

aloisdg commented Jul 2, 2015

style-guide, code and naming conventions by the organization Regexps.

@tunnckoCore
Copy link

@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. :)

@hueitan
Copy link
Collaborator

hueitan commented Jul 17, 2015

ping @tunnckoCore Thanks for your comment 👍

@aloisdg
Copy link
Owner Author

aloisdg commented Jul 25, 2015

I join @huei90 to thank you, @tunnckoCore , for the comment.

@aloisdg aloisdg closed this as completed Sep 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants