BTR - Search Integration Update
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Currently we have code in BTR that updates both search apis directly. Now both search listeners get the events via lear for the BTR filing so we can decouple BTR from needing to map things to search.
Need to make changes to:
- bor-search-updater (call btr for filing details / map + update)
- reg-search-updater (call btr for public details / map + update)
- btr-api (remove search svcs / add public details call)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the event flow across bor-search-updater, reg-search-updater, and btr-api, focusing on how filing and public details are currently mapped and updated. Done means both search updaters obtain the required details from BTR and btr-api no longer directly updates the search services.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, backend, distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100