You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Possible Solution
Seems to be a logic error in line 86 of vendor/api-platform/symfony/Bundle/Resources/views/SwaggerUi/index.html.twig but I do not understand the reason for the multiple checks present in that line so I do not have a specific suggestion on how to change it. Maybe leftovers from a previous version of this template?
(carriage returns added by me for readability)
{% if not graphQlEnabled or graphiQlEnabled %}
<a {% if graphiQlEnabled %}href="{{ path('api_graphql_graphiql') }}"{% endif %} class="graphiql-link">GraphiQL</a>
{% endif %}
Additional Context
I am using it with Symfony, but that fork directed me here for issues. If I can get some clarity on the intent of the nested checks, I could look at making a PR for this.
I dumped the graphiQlEnabled value and observed it is set to false, so the href is not present, but the text still appears on the page.
The text was updated successfully, but these errors were encountered:
I just went to double-check my notes on this, and it looks like I might have made a mistake with my cache because I can no longer reproduce it. I'm closing this for now so as not to waste anyone's time. Thank you.
API Platform version(s) affected: 4.1.7
Description
Cannot disable footer link
Other API docs: GraphiQL
even when disabled by configuration.How to reproduce
Configure in api_platform.yaml, but link will still be present.
Possible Solution
Seems to be a logic error in line 86 of
vendor/api-platform/symfony/Bundle/Resources/views/SwaggerUi/index.html.twig
but I do not understand the reason for the multiple checks present in that line so I do not have a specific suggestion on how to change it. Maybe leftovers from a previous version of this template?(carriage returns added by me for readability)
Additional Context
I am using it with Symfony, but that fork directed me here for issues. If I can get some clarity on the intent of the nested checks, I could look at making a PR for this.
I dumped the
graphiQlEnabled
value and observed it is set to false, so the href is not present, but the text still appears on the page.The text was updated successfully, but these errors were encountered: