Skip to content

Latest commit

History

History
37 lines (24 loc) 路 1.6 KB

File metadata and controls

37 lines (24 loc) 路 1.6 KB

Contributing to Practical Fullstack Challenges

First off, thank you for considering contributing! It's people like you that make this tool great.

馃洜 How can I contribute?

1. Adding a New Solution

Found a challenge that doesn't have a solution in your favorite language (e.g., PHP, Python, Go)?

  1. Navigate to the challenge folder.
  2. Create a new file in the solutions/ folder following this naming convention: solution-[language].[extension] (e.g., solution-python.py).
  3. Add your code with comments explaining the logic (Space & Time complexity analysis is a plus!).

Tip: If you use a compiled language (like Java or Go), please include instructions on how to run it in the comments.

2. Adding a New Challenge

If you have a good interview question you've encountered:

  1. Create a new folder inside the appropriate category (e.g., challenges/02-array-object/my-new-challenge).
  2. Copy the content from templates/CHALLENGE_README.md and fill it in.
  3. Provide at least one working solution in the solutions/ folder.

馃殌 Pull Request Process

  1. Fork the repository.
  2. Create a new branch (git checkout -b feat/add-python-solution-fizzbuzz).
  3. Commit your changes (git commit -m 'Add Python solution for FizzBuzz').
  4. Push to the branch (git push origin feat/add-python-solution-fizzbuzz).
  5. Open a Pull Request.

馃摑 Code Style

  • Keep code clean and readable.
  • Use meaningful variable names (avoid x, y, arr if possible).
  • Explain the "Why": Since this is an educational repo, comments explaining why you did something are more important than the code itself.