feat(fakers): ability to add fakers#8
Open
bartoszmajsak wants to merge 1 commit intoinstrumenta:masterfrom
bartoszmajsak:faker
Open
feat(fakers): ability to add fakers#8bartoszmajsak wants to merge 1 commit intoinstrumenta:masterfrom bartoszmajsak:faker
bartoszmajsak wants to merge 1 commit intoinstrumenta:masterfrom
bartoszmajsak:faker
Conversation
lirik90
pushed a commit
to lirik90/swagger2jsonschema
that referenced
this pull request
Mar 30, 2024
…ns/docker/build-push-action-5.2.0 Bump docker/build-push-action from 5.1.0 to 5.2.0
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As mentioned in #7 I am playing with fuzzy testing and for that I'm using https://github.com/json-schema-faker/json-schema-faker. I wanted to have an option of adding
fixerfields while generating the schema, so I can influence how particular field is generated. I'm aware this can be done as part of OpenAPI extension in k8s upstream, but was wondering if we couldn't have this flexibility at this level for testing purposes.