event-dispatcher | repository holds all interfaces

While my end goal is to prevent Swagger UI from losing authentication upon browser reload, I believe I might have found a solution assuming swagger-ui parameters can be changed when using api-platform, and described it at the tail of this post.

A REST API uses Symfony, API-platform and authenticates using JWT and documentation is provided by swagger-ui. On the swagger-ui page, after submitting the apiKey, future requests include it in the header, however, if the browser is refreshed, the authorization token is lost.

There has been some discussion on this topic primarily on this github post and some on this stackoverflow post, and the general consensus seems to be that swagger-ui there is no "official" way to persist tokens.

Overall Swagger UI does not store tokens, and probably on purpose. There is no switch to enable this, but looks like there are little things that can be done to remember a token via cookie, local storage, indexdb, etc and when the page is reloaded, populate the token back in.

The swagger configuration documentation, however, appears to have an Authorization parameter which will allow the authorization data to be persisted upon browser refresh.

• Parameter name: persistAuthorization
• Docker variable: PERSIST_AUTHORIZATION
• Description: Boolean=false. If set to true, it persists authorization data and it would not be lost on browser close/refresh

Assuming I correctly interpret the Swagger documentation, how can the persistAuthorization parameter be set to true?

When modifying config/api_platform.yaml to set persistAuthorization, I received errors Unrecognized option "persistAuthorization" under "api_platform.swagger.api_keys.apiKey". Available options are "name", "type". and Unrecognized option "persistAuthorization" under "api_platform.swagger". Available options are "api_keys", "versions".

Sometimes when Travis CI is building my package, there's a short list of dependencies, like so:

I would like to use a DataProvider for a password reset by token. I have a custom operation on the User entity

I'm quite new at Symfony and struggle with this issue for my internship, when trying to run the project locally :

I'm trying to add an EventListener to my Symfony form but I have a problem with the first parameter $listener of $builder->addEventListener. I want to use FormEvents::POST_SUBMIT to generate a new field after the submit. Basically I want to display list of cities based on the postal code. The error tells me that the object is of the wrong type but I don't see which object I could use instead because the documentation tells me to do so. I'm working on Symfony 5.2

Here is my form code and the error :

Using php 7.2

My website is down since composer update. The issue seems not on the updated packages themselves (I run them in dev environment without problems, too). It seems that 'only' the cache cannot clean itself correctly.

I am trying to use composer require to install some drupal modules from within a docker container that I'm using for my development environment, and I'm getting an error message that I don't understand. I've looked online for the documentation but most of the sources out there seem to be about how to resolve dependency issues, but I'm more interested in understanding the error message itself so I can't solve this problem in the generic case.

We have the below contents on composer.json with dependencies and scripts. This comes from a legacy project where the vendors directory was pushed to GitHub. We're trying to remove that vendors directory from the repository to make its creation a part of the build process.