Skip to content

Commit e5c1a0e

Browse files
authored
Merge pull request #33 from devvsakib/devvsakib
added solution file template
2 parents e88e257 + f7efb20 commit e5c1a0e

File tree

1 file changed

+40
-0
lines changed

1 file changed

+40
-0
lines changed

README_template_for_solution.md

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
# SR NO folder-name level
2+
sr-> 0012/0013
3+
foldername -> FizzBuzz
4+
level -> (L-B) [if advance problem use A, indermediate I, beginner B]
5+
Example: # 0005 mostFrequentItem ( L-I )
6+
7+
## Problem
8+
Your problem.
9+
10+
## Solution
11+
12+
```javascript
13+
// solution code here [dont be confuse, solution code must be in js file too]
14+
```
15+
16+
## How it works
17+
use bullet point, describe step by step. to use bullet, use "-"
18+
ex: "- We added new value"
19+
20+
21+
## References
22+
Add references, like if you added a problem that use loop or node, link a resource file
23+
ex- "- [Wikipedia] (https://en.wikipedia.org/wiki/Fizz_buzz)"
24+
like thise:
25+
- [Wikipedia](https://en.wikipedia.org/wiki/Fizz_buzz)
26+
- [GeeksforGeeks](https://www.geeksforgeeks.org/fizz-buzz-program-python/)
27+
- [StackOverflow](https://stackoverflow.com/questions/171765/what-is-the-best-way-to-implement-the-fizzbuzz-test)
28+
29+
30+
## Problem Added By
31+
Same as reference, use your any social links
32+
- [GitHub](https://www.github.com/devvsakib)
33+
- [LinkedIn](https://www.linkedin.com/in/devvsakib)
34+
- [Twitter](https://twitter.com/devvsakib)
35+
36+
37+
## Contributing
38+
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
39+
40+
Please make sure to update tests as appropriate.

0 commit comments

Comments
 (0)