Properties #101
Open
Properties #101
Conversation
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
The search method does not fetch properties unless explictly specified on the query. In case the key of the property is unknown, the issue entrypoint is required
|
Hi @turran, 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. |
|
You did it @turran! Thank you for signing the Singer Contribution License Agreement. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description of change
Add support for fetching issue's properties. The current REST entrypoint used does not include properties, so another fetch to the server is required. The extra fetch is conditional, it checks if the property Properties in the schema is selected.
Manual QA steps
Inspecting the records to be synced into a target shows the properties as JSON objects correctly
Risks
The approach is the same as the fields property, but I don't know the internal process on how a new column/table is generated on the target side.
Rollback steps
Revert this branch