Comments (4)
Hi @gregorwolf,
I was wondering what the /$metadata
path would state and checked the OData Transformer you linked above. Result is
"/$metadata": {
"get": {
"summary": "$Metadata endpoint",
"operationId": "$metadata/get",
"responses": {
"200": {
"description": ""
}
}
}
}
Now I wonder how this would be helpful. Could you please provide a use case?
Thanks in advance
from odata-openapi.
In my current scenario there is an API management system that only allows requests that match the OpenAPI specification.
from odata-openapi.
What requirements does your API management system have regarding preciseness of the request description? The example above basically allows any kind of response.
Would it be an option for you to reflect the specialties of your API management system in a post-processing step that adds a system-specific /$metadata
path?
from odata-openapi.
Hey Ralf, that's pretty much what the converter site described above does, it's not overly complex to do to be honest.
Here's the few lines of code we use to add it.
from odata-openapi.
Related Issues (20)
- Specific OData XML file cannot be converted, only .tmp file is created HOT 2
- Error: spawnSync java ENOENT HOT 3
- Unexpected Token Error HOT 3
- Edm.Int64 PrimitiveType translated to anyOf["string", "integer"] HOT 2
- Support for /$count operation HOT 4
- Openapi specification only documents DELETE and PATCH for single entity URLs HOT 6
- SAP R3 FunctionImport: Documentation Tag in Parameter fails the generation HOT 4
- Property sap:label is not handled HOT 2
- <Key> in Schema creates errors HOT 1
- Empty output while converting `https://graph.microsoft.com/beta/$metadata` HOT 6
- FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory HOT 5
- More than two annotation target path segments HOT 5
- Unexpected node HOT 4
- Error in Conversion .edmx to OpenAPI format HOT 1
- documentation item HOT 2
- Could it be possible to generate for a part of the odataModel ? HOT 31
- Support annotation Core.ComputedDefaultValue
- TypeError: model.element(...).find is not a function HOT 4
- Covert XMl to open api failes HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from odata-openapi.