Roberto Polli

Legacy context API usage

4

## I expect No warnings ## Instead - [ ] Warning: Legacy context API has been detected within a strict-mode tree. ``` The old API will be supported in all...

## This PR Adds the super-linter

## This PR adds supports for skipping rules. ## It's done - [x] add a skip array in the parse() function - [x] remove Spectral rules after loading the ruleset...

## Suggesting interoperable names @fabiofumarola Here I inserted some references to interoperable names, which I translated to swagger v2. If you want to merge something in the shared references let...

## I expect - pagination to conform to new specs https://github.com/ioggstream/openapi-samples/blob/master/openapi-v3/schema/components.yaml - use `offset` for paging ## instead - uses `page`

OpenAPI v3 spec files

3

## I wish To find OpenAPI V3 spec files ## Instead I just find Swagger V2 spec files ;) ## Notes if you need support in the conversion, I could...

Document the usage of Gavel Specs

1

## I expect The documentation reference the usage of [Gavel specifications](https://docs.apimatic.io/advanced/swagger-test-cases-extensions/#specifying-test-case-using-gavel-specification)

Question: how to contribute suggestion to fiware openapi specs?

1

Questions: - @jason-fox @fgalan on which repo can I contribute / PR to fiware openapi specs? - are those specs just the autosync/conversion from another source?

Add OpenAPI 3+ Spec

2

## I wish this API to provide an OAS 3+ specification

## Questa PR - considerazioni valide anche per sw proprietario - aggiunto SAST - fix editoriali