NavigationProperty has all possible methods, while base endpoint only has GET available.
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Reproduce the conversion with the Business Central EDMX and compare the generated methods for the base endpoint and its NavigationProperty endpoints. Start with ConvertSettings, including RequireDerivedTypesConstraintForBoundOperations, and inspect the converter entry point used by OoasUtil. Done means nested endpoints expose only methods actually available for them.
Written by the indexing model from the issue text.
Description
Im pretty new to C# development, so let me know if i need to include more details!
I am trying to use metadata (edmx file) from Business Central to generate swaggerUI docs for our custom API, but im having issues with navigation properties.
The base endpoint gets converted properly, only showing the valid methods for the endpoint:
But the NavigationProperty endpoints seem to get generated with no regard to the base endpoint:
I tried to use the "RequireDerivedTypesConstraintForBoundOperations" parameter in the ConvertSettings of the OoasUtil tool, with no luck.
Is there a way for me to either configure the converter or edit my edmx file in order to only show actually available methods for "nested" endpoints?
NavigationProperty for EntityType company:
EntitySet for custLedgerEntries endpoint:
- Dominant language
- C#
- Stars
- 240
- Forks
- 70
- Avg merge
- 7h 59m
- Merged PRs (30d)
- 13
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/OpenAPI.NET.OData
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/OpenAPI.NET.OData#661 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
microsoft/OpenAPI.NET.OData#852 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/OpenAPI.NET.OData#833 ·
-
status:needs-more-information
Difficulty 4/5 3-5 days Newbie friendliness 42/100
microsoft/OpenAPI.NET.OData#723 · 1 comment · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
microsoft/OpenAPI.NET.OData#720 ·
All issues in microsoft/OpenAPI.NET.OData
Similar issues
-
type/automation type/tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
t/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
ci-failure-cause test-failure
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:auth FE mvp P3
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
klasolsson81/jobbliggaren#1788 ·