Yes it does seem to be back to 'normal', all of the tests I just wrote to catch the 404 on every paged result route are failing. which is a good thing.

+100 - i am starting a conversation with kevin regarding this newly introduce 'feature'. I would have to say that it was not thoroughly thought out. Of course empty results should be returned. Of course. If you are requesting a specific resource, a 404 is appropriate, if you are tossing out a net, you should get some fish or no fish, not an oil spill.

that is good. I can now push tags into the params ctor for that route as it is essentially the 'id'.

perhaps a wiki question with a disclaimer would be better than nothing, I can generate a starting set.

@kevin - we seem to be arriving at the same place, regardless of the route. thanks for taking the time to talk about it.

@kevin - it is not complicated at all from my perspective: the single concern is whether to declare all 'number' fields in the api as double/float to accomodate the possible values represented by 'number' or add a note to the field description indicating that there will be no freakin decimal points in the value. Should an API spec make people guess? My experience is no, an API spec should server to remove amibiguities.

@kevin - I think we have a disconnect here. I am not suggesting that you CHANGE the type as listed, I am suggesting that an additional hint indicating whether the field is integral or not for those not working in JS - which is MOST of us.