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.

Sign up for GitHub

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

Jump to bottom

Add support to generate a JSON config file #908

Closed
helensilva14 opened this issue Jul 19, 2023 · 1 comment · Fixed by #1089
Closed

Add support to generate a JSON config file #908

helensilva14 opened this issue Jul 19, 2023 · 1 comment · Fixed by #1089
Assignees
@nehanene15 @helensilva14
Labels
priority: p1 High priority. Fix may be included in the next release. type: feature request 'Nice-to-have' improvement, new feature or different behavior or design.

Comments

@helensilva14
Copy link
Contributor

helensilva14 commented Jul 19, 2023 •
edited
Loading

Similar to the way we output a YAML config file, we could provide a JSON output that can be usable if someone wants to use our library in a Python code directly and not the CLI

Related #901, #924, #925, #940
@helensilva14 helensilva14 added the type: feature request 'Nice-to-have' improvement, new feature or different behavior or design. label Jul 19, 2023
@helensilva14 helensilva14 self-assigned this Aug 2, 2023
@nehanene15 nehanene15 added the priority: p1 High priority. Fix may be included in the next release. label Aug 3, 2023
@nehanene15
Copy link
Collaborator

Similar to how we support --config-file config.yaml, we should support --config-file-json config.json.

@helensilva14 helensilva14 mentioned this issue Aug 15, 2023
Closed
@helensilva14 helensilva14 linked a pull request Aug 15, 2023 that will close this issue
feat: Add support to generate a JSON config file #944
Closed
@helensilva14 helensilva14 added priority: p2 Medium priority. Fix may not be included in next release (e.g. minor documentation, cleanup) and removed priority: p1 High priority. Fix may be included in the next release. labels Aug 23, 2023
@helensilva14 helensilva14 added priority: p3 Lowest priority. This can be something deprioritized or not time sensitive. and removed priority: p2 Medium priority. Fix may not be included in next release (e.g. minor documentation, cleanup) labels Sep 21, 2023
@nehanene15 nehanene15 added priority: p1 High priority. Fix may be included in the next release. and removed priority: p3 Lowest priority. This can be something deprioritized or not time sensitive. labels Nov 3, 2023
@nehanene15 nehanene15 self-assigned this Nov 3, 2023
@helensilva14 helensilva14 mentioned this issue Jan 29, 2024
Closed
@helensilva14 helensilva14 mentioned this issue Feb 5, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nehanene15 nehanene15

@helensilva14 helensilva14

Labels
priority: p1 High priority. Fix may be included in the next release. type: feature request 'Nice-to-have' improvement, new feature or different behavior or design.
Projects
None yet
Milestone
No milestone
3 participants
@nehanene15 @helensilva14 and others