Create an include (something like https://github.com/dotnet/AspNetCore.Docs/blob/master/aspnetcore/includes/reservedRouting.md

With the info from https://github.com/dotnet/aspnetcore/wiki/MVC-Reserved-Keywords on routing. Be stronger, something like

These keywords should not be used for link generations, as model bound parameters, or top level properties.

Add the include to the 3

I am intentionally making this issue specific but I assume it could be expanded to include much more of the API.

Problem

I do not have the entire Prisma Client API perfectly (let alone roughly) committed to memory.

When I go to use it to query for many results the operations tell me nothing about what and why they will do. I only have types to work with.

I don't want to open my br

Refer black7375/Firefox-UI-Fix#17 (comment)

7k5x/Firefox-UI-Fix@85d6d04

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

Currently, few icons are not visible in dark theme. Make them visible by using theme neutral icons. May be we can make use of https://shields.io/ to generate our own kind of badges. For eg: Javascript.

Multiple Explore-related components still make use of GrafanaTheme.
Since Grafana 8.0 introduces GrafanaTheme2 and deprecates GrafanaTheme we should migrate to the new theme.

This should probably be done in multiple small PRs that target a small amount of components to make review easy.

Also the following data sources have components that need to be migrated:

• Elasticsearch