getappmap / getappmap/appmap-js
External service routes have a sidebar panel representation in the UI
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 18
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
External services exist as top level code objects. Their children, external service routes, have no frontend representation in the UI. In other words, if you view an external service in the frontend, the next level down is events - where it should be routes.
This feature is necessary in cases where an external service is issued repeat requests. In this case, the user may want to hide the route that appears too frequently. Currently the only option is to hide the external service as a whole.
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 by locating the frontend representation of external services and how their children are currently rendered, especially the events level. Add the missing external service route level so routes appear beneath their service and can be hidden independently; done means the sidebar shows routes before events and supports hiding an individual route.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100