Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

✨(gentest): Better gentest specific configuration #893

Closed
1 task done
Tracked by #866
raxhvl opened this issue Oct 14, 2024 · 0 comments · Fixed by #892
Closed
1 task done
Tracked by #866

✨(gentest): Better gentest specific configuration #893

raxhvl opened this issue Oct 14, 2024 · 0 comments · Fixed by #892
Labels
scope:gentest Scope: Changes to gentest CLI command type:feat type: Feature

Comments

@raxhvl
Copy link
Contributor

raxhvl commented Oct 14, 2024

Currently gentest config is a JSON file. JSON configurations are verbose and does not support comments. At some point it could be benificial to migrate to Pydantic Settings or YAML.

Tasks

Preview Give feedback
  1. scope:gentest type:feat
@raxhvl raxhvl changed the title ✨ feat(gentest): Migrate gentest specific configration from JSON to YAML ✨ feat(gentest): Migrate gentest specific configration from JSON Oct 14, 2024
@raxhvl raxhvl changed the title ✨ feat(gentest): Migrate gentest specific configration from JSON ✨ feat(gentest): Better gentest specific configuration Oct 14, 2024
@danceratopz danceratopz changed the title ✨ feat(gentest): Better gentest specific configuration ✨(gentest): Better gentest specific configuration Oct 16, 2024
@danceratopz danceratopz added type:feat type: Feature scope:gentest Scope: Changes to gentest CLI command labels Oct 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope:gentest Scope: Changes to gentest CLI command type:feat type: Feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants