rest
A representational state transfer (REST) API is a way to provide compatibility between computer systems on the Internet. The concept was first outlined in a dissertation by Roy Fielding in 2000.
Here are 1,297 public repositories matching this topic...
Describe the bug
Find-one endpoint /resource/:id responses with 500 status code instead of 404, this happens with MongoDB setup.
Steps to reproduce the behavior
- Setup Strapi with MongoDB configuration.
- Create a collection (resource).
- Give
findOneaccess to the public. - Send a request to
/resource-name/any-invalid-id.
Expected behavior
404 response.
**Sys
Q&A (please complete the following information)
- Method of installation: [npm, dist assets]
- Swagger-UI version: [>=3.25.1]
- Swagger/OpenAPI versi
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?
Description
To be able to optionaly remove the google fonts dependency on any page of the api-platform.
Example
Remove the google font stylesheet in line 8 in the file api-platform\core\src\Bridge\Symfony\Bundle\Resources\views\SwaggerUi\index.html.twig depending on a configuration variable.
Context
I'm working on an intranet application for a 100000+ employees company and
Comparison table
In the future, when Ky is more mature, we should add a comparison table to the readme. Like https://github.com/sindresorhus/got#comparison
The current level of code coverage is quite good (~99.7), but it would be amazing to reach 100%.
The current code coverage report can be found in codecov.io.
If you want to get the code coverage in your machine, run the following command
npm run test:coverage-uiOnce complete, it will open a new tab in your browser with the covera
Documentation for #create_pull_request_review and #submit_pull_request_review isn't very intuitive
The documentation for submit-a-pull-request-review and create-a-pull-request-review doesn't really say what the difference is between the two. Both post a PR review to GitHub.
IMO atleast something should be mentioned as to when to use whi
Prerequisites
- Are you running the latest version of
ng-admin? Yes, running the ng-admin-demo. - Did you check the documentation? Yes.
- Did you [perform a cursory search](https://github.com/issues?utf8=✓&q=is%3Aissue+repo%3Amarmelab%2Fng-admin+rep
Is there any documentation regarding CORS preflight requests? Seems like these should automatically be configured based on the swagger definition.
I'm looking to return the verbs defined in swagger for my resources (paths) but I can't even find how to control "preFlightContinue" option.
Thanks in advance.
When using getDerivedStateFromProps the lifecycle methods of react-refetch are not called.
I suppose react-refetch should be updated to use the appropriate methods.
It would be nice to have a note or two on which OAS versions this project supports.
Similar to https://github.com/swagger-api/swagger-ui/#compatibility
cc @webron
It looks like sendgrid is currently only used to reset user passwords. If that is the case it would be nice to have it also used to send a confirmation email upon user registration, so that it can be properly validated.
I suppose this would require the use of a unique email validation token.
See: https://gist.github.com/ericelliott/f3c2a53a1d4100539f71
Advantages
See: https://medium.com/javascript-scene/you-might-not-need-typescript-or-static-types-aa7cb670a77b
- autocomplete and type inference with most IDEs
- doesn't require passing Log objects for every call (although it's encouraged)
- other non-required parameters (such as
query) can be omitted - much easier to a
-
Updated
May 4, 2019 - JavaScript
In dareid/chakram#6 (comment) I note the inclusion of the extra word 'comprise' for request assertion chains.
I can't find documentation for this keyword through an API search or elsewhere on the web.
It may be because one of the unfortunate costs of building sentence-like build chains - is that each function is a dictionary word not a distinctive comp
`app.use(cache('5 minutes'))` will cache all routes, regardless of methods like `GET` and `POST`
It turns out if we do app.use(cache('5 minutes')), it will cache all routes, regardless of methods like GET and POST. However, for methods like PUT and POST, in many cases this implied update on the server side and shall not be cached. Should we add documentation or functionality to make supporting such case more easily?
-
Updated
Oct 30, 2019 - JavaScript
#1022 contains only methods but we need properties with types and short description
@o-rumiantsev @nechaido
Was getting a getState() is not a function error when trying to use the async() way of dispatching an async action, and after hunting through the issues I discovered that lexich/redux-api@02eddbf made all the dispatches return promises (awesome!! ^_^). It was hard to track down; would be awesome if the docs mentioned this somewhere.
-
Updated
Apr 6, 2020 - JavaScript
-
Updated
Apr 12, 2020 - JavaScript
When I visit /swagger-stats/ui, it seems that request will stay in processing status for statistics.
And I see [api_all_request_in_processing_total] growing when I visit /swagger-stats/ui.
Is that correct? The swagger-stats version I used is 0.95.6.
-
Updated
Apr 5, 2020 - JavaScript
As it currently is, the action bar does not give users the option to cancel their changes to the edited fields. A cancel button would be a great addition to the action bar.
// Diet Server
var server = require('diet')
var app = server()
app.listen(8000)
// Socket.io
var io = require('socket.io')(app.server) // <-- use app.server
// Listen on websocket connection
io.on('connection', function(socket){
console.log('a user connected');
});
// Now you can access socket.io from client side with:
// http://localhost:8000/socket.io/socket.io.js
Given the immense popularity of Docker and the need to harden it different per platform (see ideas below) - we'd like to start writing a Docker best practices section.
You're welcome to contribute ideas and write best practices - writing and brainstorming will people is an amazing way to deepen your Docker understanding.
At first, we want to collect ideas for best practices, solidify a list