Nice! The idea of having a friday leetcode problem for my team has been kicked around to try and keep us on our toes when it comes to solving these style problems and preventing atrophy of this part of our brain. Might try wrapping this cli in some kind of web ui or adding it to our slackbot
Show HN: Openleetcode – Local LeetCode runner where tests live in the repo
11–20 of 28 posts
Re: Show HN: Openleetcode – Local LeetCode runner where tests live in the repo
#12[deleted]
Re: Show HN: Openleetcode – Local LeetCode runner where tests live in the repo
#13[deleted]
[deleted]
Re: Show HN: Openleetcode – Local LeetCode runner where tests live in the repo
#14Re: Show HN: Openleetcode – Local LeetCode runner where tests live in the repo
#15[deleted]
Re: Show HN: Openleetcode – Local LeetCode runner where tests live in the repo
#16[deleted]
Re: Show HN: Openleetcode – Local LeetCode runner where tests live in the repo
#17Why is leet code even a thing past 2024
Re: Show HN: Openleetcode – Local LeetCode runner where tests live in the repo
#18What a great idea for a project. Will try out. Any thoughts on supporting a CLI (or TUI) interface for browsing through the problem sets locally (titles, descriptions, difficulty, etc.)? On that note, open to contributions? And much respect for choosing Haskell.
In our tests we don't store any metadata other than the ID and the title, and to be honest, I think that's beyond the scope of this project.
Re: Show HN: Openleetcode – Local LeetCode runner where tests live in the repo
#19Why is leet code even a thing past 2024
Because it's fun!
Re: Show HN: Openleetcode – Local LeetCode runner where tests live in the repo
#20Why is leet code even a thing past 2024
[dead]