Here is a list of links that return 404

https://apility.io/apidocs/
http://developer.linkedin.com/docs/rest-api
https://sentim-api.herokuapp.com/ works
https://quarantine.country/coronavirus/api/ works

https://blog.mugenmonkey.com/2017/09/10/ds3-api.html
https://developer.walmartlabs.com/docs
https://taylor.rest

Please feel free to add more broken links when you find t

• nvim --version:

NVIM v0.5.0-dev+1339-g5d9c56012
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: C:/Program Files (x86)/Microsoft Visual Studio/2017/Enterprise/VC/T
ools/MSVC/14.16.27023/bin/Hostx86/x64/cl.exe /DWIN32 /D_WINDOWS /W3 /MD /Zi /O2
/Ob1 /DNDEBUG /W3 -D_CRT_SECURE_NO_WARNINGS -D_CRT_NONSTDC

Describe the bug
Using xframe ALLOW-FROM throws error in console: Invalid 'X-Frame-Options' header encountered when loading 'https://api.dev.mysite.com/uploads/my-file.pdf': 'ALLOW-FROM dev.mysite.com' is not a recognized directive. The header will be ignored.

https://strapi.io/documentation/v3.x/concepts/middlewares.html#response-middlewares
instructions for xframe indicate `ALLOW-FR

First check

• I added a very descriptive title to this issue.
• I used the GitHub search to find a similar issue and didn't find it.
• I searched the FastAPI documentation, with the integrated search.
• I already searched in Google "How to X in FastAPI" and didn't find any information.
• I already read and followed all the tutorial in the docs and didn't find an answ

Is your feature request related to a problem? Please describe.

I try to execute my first GET request and get this result:

I think the first-time-user experience could get improved here.

The hint to F12 vanishes soon, and I think accessing the error message via F12 is not a

Found an issue with a fresh install of Directus on a database with existing foreign keys/ relationships setup. The Many to One interface doesn't display when you enable it for existing foreign keys. Might be caused by the foreign key field not existing in the directus_relations table, as this table remains empty when enabling the interface.

Exact steps to reproduce this issue
- Create

Currently the git hook runs pre-commit, and will write the linter changes to the file, meaning the dev's commit is usually successful, but without linter fixes. The dev then has to make a second commit to include linter fixes

Instead, yarn lint:check should run only before a push, and would provide the dev linter errors, so that the hook aborts the push until the linter is satisfied (by runni

Bug Report Checklist

• [~] Have you provided a full/minimal spec to reproduce the issue?
• Have you validated the input using an OpenAPI validator, yes I used the validate function of the api generator
• [5.0.0 ] What's the version of OpenAPI Generator used?
• Have you search for related issues/PRs?
• What's the actual output vs expected output?