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

Allow passing literal JSON strings instead of file paths #110

Closed
wants to merge 3 commits into from

Conversation

dcereijodo
Copy link

Extended load_json function in the utils to accept literal JSON strings instead of file paths. load_json will try to interpret the input string as JSON and fallback to interpret it as a file path when JSON parsing fails.

Closes #109

@cmerrick
Copy link
Contributor

Hi @dcereijodo, thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes.

@cmerrick
Copy link
Contributor

You did it @dcereijodo!

Thank you for signing the Singer Contribution License Agreement.

@judahrand
Copy link
Contributor

Looks really good! Any chance this can get merged? @cmerrick

@judahrand
Copy link
Contributor

@cmerrick

@dcereijodo
Copy link
Author

Closing this as it doesn't look like it's getting merged.

@dcereijodo dcereijodo closed this Feb 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Support for inline configuration strings
3 participants