You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
leetgo is a fantastic tool for pulling problems, generating skeleton code, testing locally, and submitting — essentially covering the full solve-and-submit workflow.
However, one thing I often find myself doing after solving (or getting stuck on) a problem is switching to the browser to read the official editorial or top community solutions. It would be great if leetgo could streamline this step as well.
Proposal
Add a new command (e.g. leetgo solutions <problem> or leetgo editorial <problem>) that fetches and displays solution content directly in the terminal. Possible scope:
Official editorial — the article provided by LeetCode under the "Editorial" tab.
Top community solutions — highest-voted solutions from the "Solutions" tab, optionally filtered by language.
The output could be rendered as Markdown in the terminal, or simply printed as plain text.
Why
Keeps the entire workflow inside the terminal without context-switching to a browser.
Pairs naturally with the existing pick → test → submit flow — after submitting, you can immediately review better approaches.
LeetCode exposes editorials and community solutions via its GraphQL API, so the data is accessible.
Open Questions
Should this be a standalone command or a flag on an existing command (e.g. leetgo info --solutions)?
Should it require the user to be logged in (some editorial content is premium-only)?
Any concerns about LeetCode ToS when fetching editorial content programmatically?
Would love to hear thoughts from the maintainer and community. Happy to help with implementation if there is interest!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Background
leetgo is a fantastic tool for pulling problems, generating skeleton code, testing locally, and submitting — essentially covering the full solve-and-submit workflow.
However, one thing I often find myself doing after solving (or getting stuck on) a problem is switching to the browser to read the official editorial or top community solutions. It would be great if leetgo could streamline this step as well.
Proposal
Add a new command (e.g.
leetgo solutions <problem>orleetgo editorial <problem>) that fetches and displays solution content directly in the terminal. Possible scope:The output could be rendered as Markdown in the terminal, or simply printed as plain text.
Why
pick → test → submitflow — after submitting, you can immediately review better approaches.Open Questions
leetgo info --solutions)?Would love to hear thoughts from the maintainer and community. Happy to help with implementation if there is interest!
Beta Was this translation helpful? Give feedback.
All reactions