Updates to support AEP Mobile Edge Events
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
### Expected Behaviour
Match all AEP Mobile Edge Response events in a Project Griffon session. Including error events.
### Actual Behaviour
I’ve run into a few inconsistencies with edge response events vs SDK v5 response events.
In Edge, the ACPExtensionEventSource is being overwritten with the konductor handle type so it doesn’t contain the v5 value: com.adobe.eventsource.responsecontent
The ACPExtensionEventData payload is coming back as an array instead of an object
The request event identifier in edge events is requestEventId but in SDK v5 it’s requestEventIdentifier
### Reproduce Scenario (including but not limited to)
No schemas or code exist to match AEP Mobile Edge Error Response events.
Current matchers for AEP Mobile Edge Response events only match events where Konductor handle types have not been applied.
#### Steps to Reproduce
#### Platform and Version
#### Sample Code that illustrates the problem
#### Logs taken while reproducing problem
Contributor guide
Research direction
Start by locating the schemas and matchers for AEP Mobile Edge Response events in the TypeScript toolkit, then compare their handling with SDK v5 response events. Done means matching normal and error events while preserving the expected extension event source, object payload, and request event identifier.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100