Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Potential error in Telco specification #634

Open
samWighton opened this issue Mar 8, 2024 · 2 comments
Open

Potential error in Telco specification #634

samWighton opened this issue Mar 8, 2024 · 2 comments
Assignees
@nils-work
Labels
Non-breaking change A change that is not expected to result in a new endpoint version. Proposal made The DSB has proposed a specific change to the standards to address the change request Telco
Milestone
v1.31.0

Comments

@samWighton
Copy link

samWighton commented Mar 8, 2024 •
edited by nils-work

In the Telco specification.

The 'TelcoAccountDetailResponseData' Schema is a combination of the three schemas

"#/components/schemas/TelcoAccountBase"
"#/components/schemas/TelcoAccount"
"#/components/schemas/TelcoAccountDetail"

This leads to multiple 'properties' called 'plans'.

Nils Berge mentioned that this may be an error.

In the case this is intentional, should a particular property take precedence ?

Thanks

DSB Proposed Solution

The proposed solution can be found through the staging link provided in this comment.
@nils-work nils-work added the Telco label Mar 8, 2024
@nils-work nils-work self-assigned this Mar 26, 2024
nils-work added a commit to ConsumerDataStandardsAustralia/standards-staging that referenced this issue Mar 26, 2024
@nils-work
Removed duplicate TelcoAccount schema
ada44fd 
Addresses: ConsumerDataStandardsAustralia/standards-maintenance#634
@nils-work
Copy link
Member

A change to address this issue has been staged for review here: ConsumerDataStandardsAustralia/standards-staging@release/1.30.0...maintenance/634

image

@nils-work nils-work added this to the v1.30.0 milestone Apr 2, 2024
@nils-work nils-work added the Proposal made The DSB has proposed a specific change to the standards to address the change request label Apr 2, 2024
@nils-work nils-work added the Non-breaking change A change that is not expected to result in a new endpoint version. label Apr 16, 2024
@nils-work nils-work removed this from the v1.30.0 milestone Apr 26, 2024
@nils-work nils-work added this to the v1.31.0 milestone May 20, 2024
@nils-work
Copy link
Member

A decision on this change was made with other items in Maintenance Iteration 18, but this issue was not included in version 1.30.0.
This issue will be included in the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nils-work nils-work

Labels
Non-breaking change A change that is not expected to result in a new endpoint version. Proposal made The DSB has proposed a specific change to the standards to address the change request Telco
Projects
Data Standards Maintenance
Status: In Progress: Staging
Milestone
v1.31.0
Development

No branches or pull requests
2 participants
@samWighton @nils-work