Order matters when adding route with HEAD method

[YuriiMotov]

Currently there is a pitfall with adding a route for HEAD method. If you add route with GET method and then add a route with HEAD method for the same path - explicitly added route with HEAD method will be ignored. Automatically added HEAD method will be used.

Code example:

from starlette.applications import Starlette
from starlette.responses import PlainTextResponse
from starlette.routing import Route

calls = []


async def homepage(request):
    calls.append("GET")
    return PlainTextResponse("Homepage")

async def head(request):
    calls.append("HEAD")
    return PlainTextResponse("")


routes = [
    Route("/", endpoint=homepage),
    Route("/", methods=["HEAD"], endpoint=head),
]

app = Starlette(routes=routes)


def test_head_method():
    from starlette.testclient import TestClient

    client = TestClient(app)

    response = client.head("/")
    assert response.status_code == 200
    assert response.text == ""
    assert calls == ["HEAD"]

I'd like to discuss an idea. What if:

• don't automatically add HEAD method for GET-routes
• handle this during the routing: if there is a route with HEAD method (explicitly added by developer) - use it, otherwise use route with GET method

?