AcceptContentTypes per source, Fix isValidJson issue with arrays #206
Conversation
This file contains 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
|
There is a lot more going on. in this bucket.. |
|
@valentinedwv I know this is just as draft but I tested this against one of my sources with the "array graph" format and it worked perfect. Thanks! I need to get my prov stuff fixed up and merged into dev. At that point it might be nice to have a session and merge things into master again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Preps for JSON Profiles, by setting up acceptcontenttype and jsonprfile properties on sources
fixes the if is array is valid JSON issue.
Does not fix the need that like aquadocs we may need to split these things up into individual files.