Change Listeners/Event Notifications for DA content
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
Research direction
Start by mapping where DA content changes are handled and how the Search system currently receives updates. Clarify whether the change log or client webhooks is the delivery mechanism, define the four required events, and consider the work complete when each event can notify Search reliably.
Written by the indexing model from the issue text.
Description
To ensure features like Search remains consistent and up-to-date, we need to implement change listeners for the content. These listeners will monitor changes in the underlying content and notify the Search system to make necessary updates to indexed documents. Basic change events are needed to support this feature, like :
- file created
- file moved
- file deleted
- file modified
There could be a periodic post of the change log similar to journaling APIs , or a way to register client application's own webhook to receive these events.
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the 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 adobe/da-admin
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
NationalSecurityAgency/skills-service#4052 ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/gh-aw-workshop#4251 ·
Maintainers usually reply within 1 day
-
customer-support needs-triage Platform(Default)
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Leonxlnx/taste-skill#129 ·
Maintainers usually reply within 1 day