Quality Assurance Projects - Sudoku Solver clearer instructions on logic
See original GitHub issueDescribe your problem and how to reproduce it: There are two major questions I had while I was doing this project, and it seems like other people also had similar issues.
1.) (There’s a similar issue to this already here, but this question deals with conflicting row/column/region.)
Q: Do we need to indicate if the value at a coordinate is conflicting with the final solution or with what is currently on the board?
If something could indicate that you only need to figure out checkRow/Column/RegionPlacement in sudoku-solver.js
with what is currently on the board rather than checking with the final solution, that would help immensely.
2.) Q: For the solve()
method in sudoku-solver.js
, does it need to check against solution logic provided elsewhere in the backend only on the test inputs, or do we need to provide the solve logic ourselves for ANY given puzzleString input?
I received several conflicting answers when I asked on Discord, but I believe the right answer is that I need to provide the logic myself? Making this clearer on the /learn page by saying that we need to return the solved string with our own logic in solve()
would be helpful.
These are probably not the clearest answers, but these were sufficient in helping me answer my questions that I had about this.
Add a Link to the page with the problem: https://www.freecodecamp.org/learn/quality-assurance/quality-assurance-projects/sudoku-solver
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top GitHub Comments
I am fine with adding this as well.
Hi, I’ve opened my first PR in this repo for this issue. Please take a look when you have a chance!