fix(Linear Node): Fix issue with data not always being returned #9273
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
Joffcom
changed the title
n8n-assistant
bot
added
n8n team
…bug-cannot-read-properties-of-null-when-requesting-251-or
michael-radency
approved these changes
May 2, 2024
Passing run #4845 ↗︎
Details:
Review all test suite changes for PR #9273 ↗︎ |
|||||||||||||||
|
✅ All Cypress E2E specs passed |
Joffcom
deleted the
node-1234-bug-cannot-read-properties-of-null-when-requesting-251-or
branch
Merged
|
Got released with |
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.
Summary
Fixes an issue with Linear not always returning data since #8587
Sets the max value for Limit to 250 following API guidelines
Related tickets and issues
https://linear.app/n8n/issue/NODE-1234/bug-cannot-read-properties-of-null-when-requesting-251-or-more-items