Switch from compiling Notification Types to Event Types#125
Conversation
SummaryThe following content is AI-generated and provides a summary of the pull request: Switch Notification Type Derivation from JSON to CDS Event AnnotationsNew Features✨ Notification types can now be automatically derived from CDS event definitions annotated with A new Changes
PR Bot InformationVersion:
|
There was a problem hiding this comment.
The PR introduces a useful feature — deriving notification types from CDS model annotations rather than requiring a hand-authored JSON file. However, there are several substantive issues: a redundant cds.load during startup that should use the already-available cds.model, a potential TypeError in resolveEnum when the channel value is not a string, a silent data loss when the struct form of @notification is used instead of flat annotation keys, and unit tests that bypass cds.reflect() and therefore do not accurately validate the production code path. Please address these before merging.
PR Bot Information
Version: 1.20.43
- File Content Strategy: Full file content
- Event Trigger:
pull_request.opened - Correlation ID:
01b9afab-28a3-4551-8db9-7abecd2e74cc - LLM:
anthropic--claude-4.6-sonnet
Plug-in currently builds and compiles from a user-written json file. This is slow and inefficient. Types also (automatically) will come from event types from cds files where events are annotated with @notification (json file remains backwards compatible).