-
Notifications
You must be signed in to change notification settings - Fork 20
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
Added a ref Resolver #105
Added a ref Resolver #105
Conversation
…he old broken ref schemas, and added a tool for resolving the refs
Worried about potential json schema failures as we haven't been able to fully test this with Data in production setups (Tested with my test instance and one live instances data, but history shows that's not enough) |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to fix those issues
tap_clickup/schemas/folder.json
Outdated
}, | ||
"color": { | ||
"type": ["null", "string"] | ||
}, | ||
"type": { | ||
"type": ["null", "string"] | ||
} | ||
}, | ||
"feature": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This doesn't look to be needed
@@ -13,6 +13,7 @@ plugins: | |||
- name: api_token | |||
kind: password | |||
select: | |||
- '!shared_hierarchy.*' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not needed
tap_clickup/schemas/team.json
Outdated
"type": ["null", "string"] | ||
} | ||
"id": { | ||
"type": "integer" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be safe I think we should add null here, as these refs haven't been heavily tested by users.
tap_clickup/schemas/team.json
Outdated
"user": { | ||
"$ref": "#/definitions/user" | ||
"id": { | ||
"type": "integer" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add nulls (similar to above comment)
tap_clickup/schemas/team.json
Outdated
"type": "object", | ||
"properties": { | ||
"id": { | ||
"type": "integer" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add nulls (similar to above comment)
Hi, thank you for the great work and support here. I am using list (folder-list) and space heavily and this fix will help us a lot. Also, we found another issue that I will share shortly with you after verifying my solution. Could you please move forward with this pull request earlier? |
Yeah I want to merge this, I just need to test that it works with target-postgres, and target-stitch. Issue is that I don't have functional testing setup to automate this for me (and I'd probably want to smoke test myself locally anyway) Next steps are
I won't have time to do this for a bit. I''ll try to, or if someone could do these tests for me or a portion of them it'd be mightly helpful! |
}, | ||
"invited_by": { | ||
"$ref": "#/definitions/user" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be nice to keep this instead of duplicating what a user is
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
noted in above comment
"type": "array", | ||
"items": [ | ||
{ | ||
"type": "object", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would be nice to keep this instead of duplicating what a user is
There's also some duplicate in the PR, I'd like to remove some of them and replace them with Refs, if someone could to that it would be very helpful as well (I hope it can work without changing the ref resolver we're using, if not we don't need to dive too hard we can just leave the duplication) |
I will ask my friends if they have capacity to help, their sprint starts the next Monday (No tomorrow). |
Data looks good from a run on my end
After review there were only a handful of properties without nulls, this shouldn't' hold up the merge as this PR puts us in a better place. |
We're all merged in, pull the latest from pypi and you should be good to go! |
Closes #104