Florent Chamfroy
Florent Chamfroy
You were right, it was not so difficult 😉
It seems that what I propose is in conflict with [`LegacyConverterTest`](https://jenkins.swagger.io/job/oss-swagger-parser-v1-pr/215/testReport/io.swagger.converter/LegacyConverterTest/).
@gracekarina what do you think is the best option ? - fix the issue on the v1 branch and update `LegacyConverterTest` https://github.com/swagger-api/swagger-parser/blob/v1/modules/swagger-compat-spec-parser/src/test/java/io/swagger/converter/LegacyConverterTest.java#L168 or - fix the issue on master in...
out of date PR
@guillaumelamirand 4.2 (and 4.3) has been released. Should we consider updating this PR? Or can we close it?
I put this PR in draft because I think we need to discuss the E2E case.
Hello. I have also migrated to 2.23.0, and now I have this kind of error when trying to synchronise files ```bash ~$ aws s3 sync folder_to_sync s3://custom/ --profile default --endpoint-url...
Gatling has been removed from our dependencies.
But when you are in the organization screen, you are not supposed to have a current environment. So you should have all groups from the organization. I can see two...
4.1.x is no longer suported. Can you target 4.2.x branch for your PR? Could you also provide some before/after screenshots? When fixes are about CSS stuffs, it's easier to validate...