duplicate endpoints on a view
Open
Nobody has claimed this yet.
bug
needs repro case
- Dominant language
- Go
- Stars
- 10.1k
- Forks
- 413
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 6
Description
We received this screenshot of a resource view:
there's really only one endpoint, but it's getting duplicated somehow. Refreshing the page fixes the issue.
Probably a bug in how we're sending down updates.
Contributor 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.
Research direction
Start by reproducing the resource view shown in the screenshot and compare its endpoint list before and after a refresh. Trace the update-delivery path for the view to find where one endpoint can be rendered twice, then add a regression test that verifies updates preserve a single endpoint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100