Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

leetcode的id和slug不匹配

Open
#3 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
api, cli

Research direction

Start at the command-line entry point exercised by cargo run 179 and trace how the API response's problem ID and slug are selected or displayed. Reproduce the reported output, then verify that the requested problem's identifier and slug correspond consistently.

Written by the indexing model from the issue text.

Description

我改了下代码输出接口获取的problem,发现id和slug并不匹配:

cargo run 179
   Compiling leetcode-rust v0.1.0 (/Users/daniel/CLionProjects/leetcode-rust)
    Finished dev [unoptimized + debuginfo] target(s) in 3.86s
     Running `target/debug/leetcode-rust 179`
id: 1057, code: rust, slug: numbers-with-repeated-digits
id: 1056, code: rust, slug: capacity-to-ship-packages-within-d-days
id: 1055, code: rust, slug: pairs-of-songs-with-total-durations-divisible-by-60
id: 1054, code: rust, slug: complement-of-base-10-integer
id: 1050, code: rust, slug: construct-binary-search-tree-from-preorder-traversal
id: 1049, code: rust, slug: minimum-domino-rotations-for-equal-row
id: 1048, code: rust, slug: clumsy-factorial
id: 1047, code: rust, slug: maximize-sum-of-array-after-k-negations
id: 1046, code: rust, slug: max-consecutive-ones-iii
id: 1045, code: rust, slug: check-if-word-is-valid-after-substitutions

Dominant language
Rust
Stars
764
Forks
145
PR merge metrics
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aylei/leetcode-rust

All issues in aylei/leetcode-rust

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.