Netcracker / Netcracker/qubership-apihub-api-diff

[FE] System doesn't show extension changes for several cases

Open
#48 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
0
Forks
2
PR merge metrics
No merged PRs in 30d

Description

xml 1.yml

Describe the bug

Due to design https://github.com/Netcracker/qubership-apihub-compatibility-suites/wiki/OAS-Extensions
System doesn't show extension changes for cases:

OAS Object Extension Classification Обоснование
1 Info Object annotation Purely documentation information about the API
2 Contact Object annotation Contact information - documentation
3 License Object annotation License Information - documentation
4 Server Object unclassified May affect the connection to the server
6 External Documentation Object annotation Links to external documentation
7 Tag Object annotation Metadata for grouping operations
21 Callback Object unclassified Affects the callback functionality
23 XML Object unclassified Affects XML serialization
26 Components Object unclassified Container for reusable components
To Reproduce
OAS Object Extension Classification Specs
1 Info Object annotation 01-info-object_after.yaml, 01-info-object_before.yaml.yaml
2 Contact Object annotation 02-contact-object_before.yaml, 02-contact-object_after.yaml
3 License Object annotation 03-license-object_before.yaml, 03-license-object_after.yaml
4 Server Object unclassified 04-server-object_before.yaml, 04-server-object_after.yaml
6 External Documentation Object annotation 06-external-documentation-object_before.yaml, 06-external-documentation-object_after.yaml
7 Tag Object annotation 07-tag-object_before.yaml, 07-tag-object_after.yaml
21 Callback Object unclassified callback2.yml,callback1.yaml
23 XML Object unclassified xml 2.yaml,xml 1.yml
26 Components Object unclassified compon 2.yml,compon 1.yaml

ER: see Extension Classification column
AR: no changes defined

Version

Backend v. develop.580c3eb
Frontend v. 3.2.1-dev.20251111164623
API Processor v. 4.2.2-dev.20251111162753

Logs

No response

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with the attached before/after specifications for the listed OAS objects, including xml.1.yml and the callback and components pairs. Trace the frontend path that classifies and renders extension changes, then verify that the displayed results match the Extension Classification column for each case.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.