-
Notifications
You must be signed in to change notification settings - Fork 90
Remove limit value clamping
#172
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
Conversation
Don't cap `limit` and let the server perform value validation. refactor(subscribe): replace legacy `t` with `tt` and `tr` Replace legacy timetoken query parameter with subscribe v2 parameters. fix(heartbeat): fix `state` query parameter Send proper object for `state` with the `heartbeat` request.
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
chore(CODEOWNERS): add new SDK maintainer Add `@mohitpubnub` as Ruby SDK maintainer.
| else | ||
| [Pubnub::Constants::MAXIMUM_HERE_NOW_COUNT, @limit].min | ||
| end | ||
| @limit = Pubnub::Constants::MAXIMUM_HERE_NOW_COUNT if @limit.nil? |
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.
So are we going to allow value more than MAXIMUM_HERE_NOW_COUNT?
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.
n/m
limit higher than 1000 and negative offset are handled on server side.
I read this now
|
@pubnub-release-bot release |
|
🚀 Release successfully completed 🚀 |
fix(heartbeat): fix
statequery parameterSend proper object for
statewith theheartbeatrequest.refactor(here-now): remove
limitvalue clampingDon't cap
limitand let the server perform value validation.refactor(subscribe): replace legacy
twithttandtrReplace legacy timetoken query parameter with subscribe v2 parameters.