Roberto Polli comments

Results 469 comments of


                                            Roberto Polli

enforce pagination to avoid resource consumption

Moreover w are now supporting versioned rulesets. we are renaming rules because Spectral 6 doesn't allow custom properties in rules: we had then to replace tags with some other mechanism....

enforce pagination to avoid resource consumption

Consider extending fitko pagination rules to support configurable parameters

enforce pagination to avoid resource consumption

@AlessioMarinelli I updated the description. See the example schema for pagination fields. https://italia.github.io/api-oas-checker/?url=https://teamdigitale.github.io/openapi/master/definitions.yaml

enforce pagination to avoid resource consumption

Feel free to post your example OAS3 and I'll provide some comments on it.

Conflicting info regarding licensing

Cc @ruphy could you please take a look? Pick the fittest ;)

Legacy context API usage

If it's not blocking, deprioritize it in this project. @emilioSp

Update highlights on editor lines accordingly to the user modifications of the text

In the old editor, I limited the re-validation rate at 1/5seconds. You could just warn the user with an icon stating that he needs to revalidate (eg. set the auto-validate...

Update highlights on editor lines accordingly to the user modifications of the text

The "validation required" icon/color should be set: - when text is altered - when the ruleset is changed

Thanks @codedust! I think that the current spectral 5.x ruleset checks that: 1. `clientCredentials` flow has `tokenUrl` but not `authorizationUrl` 2. `authorizationCode` flow has both `tokenUrl` and `authorizationUrl` afaik: 3....