Profile response detail view shows both version control messages
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 84/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python, typescript
Research direction
Start in ResponseHistoryBanner.tsx and inspect how the two version-control alerts are rendered for an old response revision. Review Response.old_versions and current_version to confirm the backend behavior, then ensure the info alert appears only for the current version or that the old-version collection excludes self. Done means an old revision shows only the warning while the current version still shows the info alert.
Written by the indexing model from the issue text.
Description
When viewing an old revision of a response in the profile response detail view, both version control banners render at once: the warning "you are viewing an old version" AND the info "this response has N old versions".
Root cause
ResponseHistoryBanner.tsxrenders the two alerts independently; the info alert is not gated on!response.supersededBy.- Backend:
Response.old_versionsfilters onsuperseded_by=self.current_version, andcurrent_versionreturnsself.superseded_by or self— so an old revision'sold_versionsreturns the whole sibling set, including itself.
Fix
Show the info alert only on the current version (and/or exclude self from old_versions).
- Dominant language
- Python
- Stars
- 29
- Forks
- 33
- Avg merge
- 23h 5m
- Merged PRs (30d)
- 24
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
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.
More from con2/kompassi
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
python
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
con2/kompassi#770 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
con2/kompassi#757 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Juniper/ansible-junos-stdlib#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
pollen-robotics/reachy_mini#1457 ·
Maintainers usually reply within 1 day
-
area:runtime good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
WATonomous/wato_f1tenth#39 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
FireDynamics/fdsreader#123 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100