Update fetchStatusMessage to handle empty offset / page
#1536
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.
Currently, using an undefined value for
offsetorpagewhen callingfetchStatusMessagereturns an Internal Server Error (http code 500) in the API.With the fact that the docs did not mention
offsetandpage, caused some confusion when interacting with this endpoint.This PR adds a default value for both
offsetandpagewhen they are not specified, similar to what is already done in the functionfetchMessages(src/api/services/channel.service.ts)Together with the docs update at EvolutionAPI/docs-evolution#16, it should solve the issues #1253, #1339, and #1533
Summary by Sourcery
Default missing
offsetandpageparameters infetchStatusMessageto prevent unhandled server errorsBug Fixes:
offsetorpageis undefined infetchStatusMessageEnhancements:
fetchMessagesby settingoffsetto 50 andpageto 1 when absent