openapi3
Here are 450 public repositories matching this topic...
Description
How can I use socket.io instead of the plain websocket integration? I guess this is more a question belonging to starlette.
Currently migrating from a flask application using flask-socketio / python-socketio
Any hint is appreciated. Thx.
Just a FYI when people start trying to submit bugs about this, mobx-react shipped a funky build which is causing broken-ness (at least when using redoc-cli bundle)
Currently breaks with an error like:
Cannot find module '..../.npm/_npx/1868/lib/node_modules/redoc-cli/node_modules/mobx-react/dist/mobxreact.js (added for searchability)
Can
First of all, the following repository has all the code (and description as well) to reproduce this problem: https://github.com/elgleidson/swagger-problem
I have the following JSON:
{
"nonNullableField": "not null",
"nullableField": null,
"nonNullableObjectField": {
"someField": "some value"
},
"nullableObjectField": null,
"nonNullableList": [
"not null"There is absolutely no documentation (other than "this is how you drop an existing file". What is the point of releasing such a product if you do not document it?
Bug Report Checklist
- Have you provided a full/minimal spec to reproduce the issue? not relevant
- Have you validated the input using an OpenAPI validator (example)? not relevant
- What's the version of OpenAPI Generator used?
- Have you search for related issues/PRs?
- What's the actual output vs expected output?
This is more of a development problem and does not affect users as it is with dev dependencies. When cloning the repository and running yarn, yarn warns about incorrect peer dependencies:
$ git clone https://github.com/apiaryio/dredd.git dredd-clean
Cloning into 'dredd-clean'...
remote: Enumerating objects: 54, done.
remote: Counting objects: 100% (54/54), done.
remote: Compressin-
Updated
Jul 5, 2020 - Python
Is your feature request related to a problem? Please describe.
I'm using Mockoon to test an HTTP client that sends a large JSON payload in the request body. Sometimes I want to verify some data sent in the request using the environment log. Currently it is a little bit frustrating without a text search function (I have to manually read through the text).
*Describe the solution you'd like
The official API docs are here
https://developers.google.com/maps/documentation/geocoding/start
I wanted to know if it would be possible to add this API's Swagger doc (and that of similar Google APIs like this).
When I run the sample from https://github.com/marshmallow-code/apispec/blob/dev/docs/quickstart.rst
the expected output
# {'components': {'parameters': {},
# 'responses': {},
# 'schemas': {'Gist': {'properties': {'id': {'format': 'int64',
# 'type': 'integer'},
#
-
Updated
Jul 4, 2020 - Java
Docs: User Guides
Is your feature request related to a problem? Please describe.
This project looks amazing, but I´m somewhat left with a no-clue of how I´m supposed to build up an API using this repository after the initial look. Is there any user guides about where to configure what and what to configure?
Describe the solution you'd like
Documentation with a walkthrough of how-to, for instance, deplo
-
Updated
Jun 30, 2020 - Go
Chore summary
Provide some guidance to the custom function writer with regards to errors
Tasks
- Add a section to
functions.md
From https://github.com/stoplightio/spectral/pull/1058/files#r408418822
@P0lip What's the effect from throwing from within a function? Does the whole process crash down? Do we get a special kind of result or a console log?
We'd get a console.l
-
Updated
Jun 28, 2020 - JavaScript
Based on #32 and discussion with @Hultner
- Have a smaller quickstart
- Link to docs in the top of the page (not only badge)
- Move documentation content to a separate document
- Share roadmap info
- Examples of errors that could be found
- Possible workflows for Schemathesis. As a part of a test suite, CI step, CLI, etc
- [Usage](https://github.com/untitaker/
-
Updated
Jun 6, 2020 - Python
Schemas, Operations, support Swagger extensions. Rather than inferring Go type names from those properties, we can also allow specifying them. Adding support for an extension like x-go-typename on those would allow for more flexibility in naming the Swagger properties more clearly since they don't have to map to the same Go type.
Add CONTRIBUTING.md
- Guidance on adding a linter new rule-action (if none of the existing ones can perform the action, or be extended)
- Expand on guidelines re: keeping commits to logical areas of the code / individual packages where possible
- Use of
conventional-commitstandard going forward - Advice not to include any
package-lock.jsonchanges PRs, for security reasons. File will be regene
I've really enjoyed using the tool for my project documentation.
In addition to API specs, however, I'm also hosting a lot of general software design documentation (that doesn't involve REST API paths at all, like class overview, state diagrams, execution concept & flow, etc.) using Markdown. Right now I'm using tags + x-tagGroups, where the description field for some tags can be hundreds an
Hello
First of all, thank you open-sourcing your code, I understand it is not easy to maintain in wild public. I am deciding which mock server generator from OpenAPI v3 specification to use and "motivation" section in readme would really help people like me to choose.
I am expecting form such docs section to get insight why you created new library instead of using already existing solutions
"false".equalsIgnoreCase(defaultValue) should be "false".equalsIgnoreCase(example)
...
} else if (BooleanProperty.TYPE.equals(type)) {
if ("true".equalsIgnoreCase(example) || "false".equalsIgnoreCase(defaultValue)) {
return Boolean.valueOf(example);
}
}
...
Looking for help to improve the examples READMEs, particularly examples/3-eov-operation READMEs
-
Updated
Jun 28, 2020 - sed
Improve this page
Add a description, image, and links to the openapi3 topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the openapi3 topic, visit your repo's landing page and select "manage topics."
Q&A (please complete the following information)