Entity Commands have a helpful feature that limits the number of results to 1000 by default. This saves you from having to wait for the page to timeout when you forget to put a vital filter on the command. However, there are times when it would be helpful to remove this limit.

Currently, you can set it to any arbitrarily high number (e.g. limit:'100000'), but that doesn't actually reflect your intent.

My proposal would be to allow the "limit" parameter to take a value ('0', or 'false'), that would remove this limit. This solution would keep the current safety net by default, but allow it to be removed if desired.

Story: I was recently asked why the capital campaign numbers on our executive dashboard stopped updating. A 3rd-party tool we were using was still showing contributions coming in but the dashboard was stuck on old numbers. It took me an embarrassing amount of time (and support from the community) to figure out that the issue was that the numbers on the dashboard were coming from an entity command and once we hit 1000 contributions, it stopped returning results. This was never its intended limit, and adding a "limit:10000" solved the problem currently, but we'll run into the same issue at 10,000. In theory, I can keep adding zeros to it, but picking an arbitrarily large number when what I actually want is no limit feels unnecessary.