-
Notifications
You must be signed in to change notification settings - Fork 17
feat(zendesk): add user_fields to user sync data #409
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
Closed
Closed
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
e158708
feat(zendesk): add user_fields to user sync data
sohan2410 9491640
add user_fields to User model
sohan2410 b07cfc3
fix test cases
sohan2410 bf076ec
fix(zendesk): make user_fields optional in User model
sohan2410 a2544b9
Merge branch 'main' into sohan/add-user-field-zendesk
khaliqgant 621a374
fix(zendesk): update user_fields type to allow any value and make it …
sohan2410 c4d11b9
Merge branch 'main' into sohan/add-user-field-zendesk
khaliqgant File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -58,7 +58,8 @@ const sync = createSync({ | |
| id: zUser.id.toString(), | ||
| firstName: firstName || '', | ||
| lastName: lastName || '', | ||
| email: zUser.email | ||
| email: zUser.email, | ||
| user_fields: zUser.user_fields | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks! You need to add this |
||
| }; | ||
| }); | ||
|
|
||
|
|
||
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
🧩 Analysis chain
🏁 Script executed:
Repository: NangoHQ/integration-templates
Length of output: 202
🏁 Script executed:
# Check the file header to verify if it's auto-generated head -n 10 integrations/.nango/schema.jsonRepository: NangoHQ/integration-templates
Length of output: 202
🏁 Script executed:
Repository: NangoHQ/integration-templates
Length of output: 202
🌐 Web query:
JSON Schema empty schema {} vs {"not": {}} anyOf semantics💡 Result:
Short answer
anyOf behavior
Notes / references
Sources
[1] JSON Schema specification (empty schema / boolean schemas).
[2] JSON Schema blog / tutorial (empty schema and "not, empty object" example).
[3] learnjsonschema: "not" keyword explanation.
🌐 Web query:
Nango v0.69.14 schema generation auto-generated files💡 Result:
Short answer: In Nango (including v0.69.14) the CLI's schema generation creates two auto-generated files under the .nango directory: .nango/schema.ts (TypeScript models) and .nango/schema.json (JSON Schema used for validation). These files are safe to version with your repo and are used by the CLI/runtime for automatic input/output validation. [1][2]
Sources
Simplify the contradictory JSON schema pattern for
user_fields.The
anyOfpattern combining{}and{"not": {}}is semantically invalid. The empty schema{}matches any value, while{"not": {}}matches nothing (since it negates the always-permissive empty schema). This makes theanyOfcondition unsatisfiable.Simplify this to:
Or, if you need to be explicit about allowing any type within the object properties, use
true:This file is auto-generated by Nango v0.69.14. The contradictory schema pattern indicates a bug in Nango's schema generation logic that should be reported or fixed upstream.
🤖 Prompt for AI Agents