>so let's see what the best "option" is to make it a good dev. experience :)If this will help developers then lets add it :)
We would need to look into this and have some special handling for producers (it's what media types a route produces that is matched with the Accept header in the request). Perhaps if the route only specifies that it produces("application/json"), and if a request has an Accept header that is "text/html", then we simply accept that too for the route and return json. But if it the route specifically produces "text/html" it should be forwarded to the view.
Please create a feature request for this and we can look into it.