-
Notifications
You must be signed in to change notification settings - Fork 25
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
fix(api): add newResponse for function SearchAllPages #770
Conversation
Make it so! |
@aircraft-cerier Thank you so much for your first contribution to this project! 🎉 I think this update makes sense and it will help us fix the bug you are experiencing, but for us to merge this change we need two things:
Please let us know if you need any help with these two requests. We look forward to merging this pull request! 💯 |
fb3f038
to
602a3a3
Compare
@afiune I think i fixed your 2 requests, let me know if i'm missing something |
Make it so! |
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.
Thanks for the contribution @aircraft-cerier!
Hi @aircraft-cerier I see one of your commits is still missing the "verified" icon. Can you do a rebase, then push with a signed commit. |
a794936
to
e020fad
Compare
Make it so! |
This is necessary as using the current response to iterate over pages corrupts data that are slices, such as the tags within imageInfo. This is beacause the memory address from the previous response will still contain data from the previous request. By creating a new response using the nextPage url we get a new spot in memory to put the next requests data. Signed-off-by: aircraft-cerier <[email protected]>
This is necessary as using the current response to iterate over pages corrupts data that are slices, such as the tags within imageInfo. This is beacause the memory address from the previous response will still contain data from the previous request. By creating a new response using the nextPage url we get a new spot in memory to put the next requests data. Signed-off-by: aircraft-cerier <[email protected]>
Signed-off-by: aircraft-cerier <[email protected]>
Signed-off-by: aircraft-cerier <[email protected]>
Signed-off-by: aircraft-cerier <[email protected]>
Make it so! |
This is necessary as using the current response to iterate over pages
corrupts data that are slices, such as the tags within imageInfo. This is because
the memory address from the previous response will still contain data from the previous request.
By creating a new response using the nextPage url we get a new spot in memory to put the next
requests data.