Diff Tool should ignore positional changes in enums
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 38/100
Direzione di ricerca
Start with the DOM serialization in Kiota’s PublicAPIExportService.cs around line 80, which the issue identifies as including enum member positions, then trace how the diff tool uses that output for breaking change detection. Check the related Graph PR and metadata change linked in the issue for context. Done means positional enum insertions no longer produce breaking change detections when enum values are unset.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Related to changes in https://github.com/microsoftgraph/msgraph-sdk-dotnet/pull/2826
The tool does detect the change in order of the enums where the timeCard member is inserted into the enum at position 8.
Removal of Microsoft.Graph.Models.workforceIntegrationSupportedEntities has an enum member timeOffReason with order 8
Removal of Microsoft.Graph.Models.workforceIntegrationSupportedEntities has an enum member timeOff with order 9
Removal of Microsoft.Graph.Models.workforceIntegrationSupportedEntities has an enum member timeOffRequest with order 10
Addition of Microsoft.Graph.Models.workforceIntegrationSupportedEntities has an enum member timeCard with order 8
Addition of Microsoft.Graph.Models.workforceIntegrationSupportedEntities has an enum member timeOffReason with order 9
Addition of Microsoft.Graph.Models.workforceIntegrationSupportedEntities has an enum member timeOff with order 10
Addition of Microsoft.Graph.Models.workforceIntegrationSupportedEntities has an enum member timeOffRequest with order 11
However, from metadata change at https://github.com/microsoftgraph/msgraph-metadata/pull/760/files#diff-eb3d3e370adab9ae29d645852adb1ce71b9206412f026061d55bd4b4b3776d48 the insertion isn't really breaking given that the value members was not set.
We should probably investigate ignoring insertions (the positional order) of enum members in breaking change detections for graph because the members end up being serialized as strings as from the SDK perspective, the change in position is really to be determined by the API.
This would involve changing the serialization of the dom to no longer have the positional parameter as seen here https://github.com/microsoft/kiota/blob/c35b901a90fbd6e19a6790d7fea8ef1ab14a5a35/src/Kiota.Builder/Export/PublicAPIExportService.cs#L80
- Lingua principale
- C#
- Stelle
- 0
- Fork
- 4
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di microsoftgraph/kiota-dom-export-diff-tool
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
Tutte le issue di microsoftgraph/kiota-dom-export-diff-tool
Issue simili
-
🐛 bug 🕒 low effort good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
guibranco/Sankhya-SDK-dotnet#654 ·
I maintainer di solito rispondono entro 1 giorno
-
a-corriger bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 86/100
christian-raj/S-Aloha#340 ·
-
遇到超大文件会卡住Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 4 giorni
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
microsoft/microsoft-ui-reactor#1626 ·
I maintainer di solito rispondono entro 1 giorno
-
Triage:Untriaged Type:Bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 79/100