Currently, the page_size field in the endpoints is configured with a maximum limit of 100:
./proto/base/v1/service.proto
uint32 page_size = 1 [
json_name = "page_size",
(validate.rules).uint32 = {
gte: 1
lte: 100
ignore_empty: true
}
];
Problem
For many use cases, having a maximum limit is restrictive, and it would be more appropriate to allow for an unlimited (lte) configuration. This restriction can hinder flexibility and usability for certain scenarios.
Proposed Change
- Modify the
lte constraint to allow for an unlimited page size:
uint32 page_size = 1 [
json_name = "page_size",
(validate.rules).uint32 = {
gte: 1
ignore_empty: true
}
];
Conclusion
Removing the upper limit on page_size will provide greater flexibility for users and better accommodate various use cases.
Currently, the
page_sizefield in the endpoints is configured with a maximum limit of 100:./proto/base/v1/service.proto
uint32 page_size = 1 [ json_name = "page_size", (validate.rules).uint32 = { gte: 1 lte: 100 ignore_empty: true } ];Problem
For many use cases, having a maximum limit is restrictive, and it would be more appropriate to allow for an unlimited (
lte) configuration. This restriction can hinder flexibility and usability for certain scenarios.Proposed Change
lteconstraint to allow for an unlimited page size:uint32 page_size = 1 [ json_name = "page_size", (validate.rules).uint32 = { gte: 1 ignore_empty: true } ];Conclusion
Removing the upper limit on
page_sizewill provide greater flexibility for users and better accommodate various use cases.