divyanshu-rawat / awesome-js Goto Github PK

View Code? Open in Web Editor NEW

22.0 3.0 44.0 134 KB

Algorithms in Javscript, including Q Learning in js.

License: MIT License

JavaScript 100.00%

documentation programming solutions algorithms

awesome-js's Introduction

Awesome-JS

Algorithms in Javscript, including Q Learning in js.

Contributing

Create your branch: git checkout -b my-new-feature
Commit your changes: git commit -m 'Add some feature'
Push to the branch: git push origin my-new-feature
Send a Pull Request
Enjoy!

Coding Conventions:

Variables name should be in camelCase.
Always put spaces around operators ( = + - * / ), and after commas.
Always use 1 tab space for indentation of code blocks.
Always end a simple statement with a semicolon.
Put the opening bracket at the end of the first line.
Use one space before the opening bracket.
Put the closing bracket on a new line, without leading spaces.
Use lower case file names without any special characters or spaces.
Function should do one thing. They should do it well.

awesome-js's People

Contributors

Stargazers

Watchers

awesome-js's Issues

DS/ALGO IN JS

Feel free to add data structures written in javascript, feel free to add programs on array, linkedlist, stack, tree, graphs etc.

Feel free to add more JS algorithms

feel free to add more js algorithms I will be more than happy to merge your PR.

Structuring of the files

Structure the algorithms based on what they act upon (strings, arrays) or based on the use cases(sorting).
Renaming the files either to include the number for all files or not at all.
Update the Readme to have contributing guidelines, this should also state whether to use tabs or spaces for indenting,
Split this task to subtasks and add them as first timer tasks :)

Feel free to add more algorithms implemented in JS

looking forward to more PR'S.

Add Stack Data Structure

I want to add a new data structure to the repo, a stack.

awesome JS

Add more applications of js in programming, even you can add awesome script in js that does cool.

Structure the algorithms

Structure the algorithms based on what they act upon (strings, arrays) or based on the use cases(sorting).

Trying to get in touch regarding a security issue

Hey there!

I'd like to report a security issue but cannot find contact instructions on your repository.

If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.

Thank you for your consideration, and I look forward to hearing from you!

(cc @huntr-helper)

Better structuring of the algorithms

Structure the algorithms based on what they act upon (strings, arrays) or based on the use cases(sorting).
Renaming the files either to include the number for all files or not at all.
After the above tasks are done, make sure the guidelines are updated to the Readme about the changes.

JS

Feel free to add node.js snippets as well that are doing something fruitful like a terminal script that let's you know your current OS.
or maybe a web scraping in node.js , or some other automation stuff using node.js.