react-component / react-component/steps
Single steps are not rendered
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 332
- Forks
- 107
- Avg merge
- 1h 8m
- Merged PRs (30d)
- 2
Description
React 18, Nextjs 12.3
import Steps from 'rc-steps';
import 'rc-steps/assets/index.css';
const { Step } = Steps;
const Tracking = () => {
const [current, setCurrent] = useState(0);
const onChange = (value) => {
console.log('onChange:', current);
setCurrent(value);
};
return (
<>
<Steps current={current} onChange={onChange}>
<Step title="Step 1" description="This is a description." />
<Step title="Step 2" description="This is a description." />
<Step title="Step 3" description="This is a description." />
</Steps>
<Steps current={current} onChange={onChange} direction="vertical">
<Step title="Step 1" description="This is a description." />
<Step title="Step 2" description="This is a description." />
<Step title="Step 3" description="This is a description." />
</Steps>
</>
);
}
The single steps are not rendered within the Steps wrapper.

Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the supplied React 18 and Next.js 12.3 reproduction, comparing the horizontal and vertical Steps examples. Trace how the Steps wrapper handles its Step children; done when single-step children render in both examples without regressing the shown multi-step behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, nextjs, react
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100