Skip to content

BDEF: fix typo - #823

Open
larshp wants to merge 5 commits into
mainfrom
hvam/bdef3007
Open

BDEF: fix typo#823
larshp wants to merge 5 commits into
mainfrom
hvam/bdef3007

Conversation

@larshp

@larshp larshp commented Jul 30, 2026

Copy link
Copy Markdown
Collaborator

incompatible, add as version 2 instead?

@larshp
larshp marked this pull request as ready for review July 30, 2026 08:38
@larshp
larshp requested a review from Copilot July 30, 2026 08:38

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Not ready to approve

Renaming a JSON field in a v1 format is an incompatible change and should be introduced as a v2 format (or explicitly support both names for backward compatibility).

Once you've addressed the issues Copilot identified, you can request another Copilot review.

This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.

Pull request overview

This PR corrects a misspelled BDEF field name (extendedBehaviorDefintionextendedBehaviorDefinition) across the ABAP type source, the generated JSON Schema, and an example JSON file.

Changes:

  • Renamed the ty_main field in zif_aff_bdef_v1 to fix the spelling.
  • Updated the BDEF v1 JSON Schema property name accordingly.
  • Updated the BDEF example JSON to use the corrected property name.
File summaries
File Description
file-formats/bdef/type/zif_aff_bdef_v1.intf.abap Renames the ABAP type component that drives JSON field naming in generated schema.
file-formats/bdef/examples/z_aff_example_bdef_extension.bdef.json Updates the example to the corrected JSON property name.
file-formats/bdef/bdef-v1.json Renames the schema property to match the corrected field name.
Review details
  • Files reviewed: 3/3 changed files
  • Comments generated: 1
  • Review effort level: Low

We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.

]
},
"extendedBehaviorDefintion": {
"extendedBehaviorDefinition": {
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants