sharks

get started

concepts

features

syntax

 

monkeys

intro

mods

REST API

 

platypuses

github

blueprints

tickets

 

everyone

support

ideas

contact

license

 

 
 

shift limit to mean total cards returned

help edit space_dashboard

Ticket

shift limit to mean total cards returned+status
open
help edit space_dashboard
shift limit to mean total cards returned+priority
low
help edit space_dashboard
shift limit to mean total cards returned+tag
Search
paging
CQL
help edit space_dashboard
shift limit to mean total cards returned+commit
 

shift limit to mean total cards returned+issues

help edit space_dashboard

Ultimately, Wagneers would like to be able to specify both a maximum number of cards for a search, and how many to return at a time. Currently, "limit" does the latter but people often expect it to mean the former. 

 

shift limit to mean total cards returned+solution

help edit space_dashboard

There is a separate ticket for replacing the functionality of what is currently called limit: duplicate limit functionality with paging

 

help edit space_dashboard

Migrating may be tricky, so the earlier this is done the better. But it should be done with plenty of warning, i.e.:

  • In an upcoming version of Wagn, make "paging" work just as "limit" does now. Deprecate the use of limit, letting people know that it will have a new meaning in a later version of Wagn. (this is duplicate limit functionality with paging)
  • In the next (or some later) version of Wagn, change "limit" so that it specifies the total number of cards being returned. Do a migration that changes existing "limit" instuctions in WQL to "paging". Make sure the release notes mention this very prominently. (this is shift limit to mean total cards returned)