fix: treat clampListLimit(0) as invalid and return default list limit - #638
Open
captainjoel2019-bit wants to merge 1 commit into
Conversation
|
@captainjoel2019-bit Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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
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.
Overview
This PR fixes inconsistent behavior in
clampListLimit()where alimitof0was treated as a valid clamp output and passed through tostreams_by_sender/StreamsModule.list(). Becauselist({ limit: 0 })silently returns zero streams, callers cannot distinguish an empty page from a caller bug such as an uninitialised variable orNumber('')evaluation. This change treatslimit <= 0as invalid input and falls back toDEFAULT_LIST_LIMIT, so0no longer produces an empty stream list.Related Issue
Fixes the reported
clampListLimit(0)issue.Changes
🐛 List-Limit Clamping Fix
src/constants.tsclampListLimit()now considerslimit <= 0invalid and returnsDEFAULT_LIST_LIMIT.NaN,Infinity) continue to fall back toDEFAULT_LIST_LIMIT.MAX_LIST_LIMITare still clamped toMAX_LIST_LIMIT.StreamsModule.list()no longer receives0as a row limit fromclampListLimit().Verification Results
clampListLimit(0)no longer returns0DEFAULT_LIST_LIMITlist({ limit: 0 })no longer silently returns an empty stream listDEFAULT_LIST_LIMITMAX_LIST_LIMITCloses #573