Return to Question

###We are withing 2 days of 1.0 and still have incorrectly documented and undocumented api parameters

I have noticed this on all sorted routes.

The min/max say that they are context sensitive to the sort type yet are documented as date.

How is a date min/max valid when sorting by, for instance votes?

###Update: this is still not resolved.

It does not affect me but the incorrectly documented min/max are still confusing people and developers.

They should be documented as string and context explained in description.

Anyone else agree?

I have noticed this on all sorted routes.

The min/max say that they are context sensitive to the sort type yet are documented as date.

How is a date min/max valid when sorting by, for instance votes?

I have noticed this on all sorted routes.

The min/max say that they are context sensitive to the sort type yet are documented as date.

How is a date min/max valid when sorting by, for instance votes?

###Update: this is still not resolved.

It does not affect me but the incorrectly documented min/max are still confusing people and developers.

They should be documented as string and context explained in description.

Anyone else agree?

###We are withing 2 days of 1.0 and still have incorrectly documented and undocumented api parameters

I have noticed this on all sorted routes.

The min/max say that they are context sensitive to the sort type yet are documented as date.

How is a date min/max valid when sorting by, for instance votes?

###Update: this is still not resolved.

It does not affect me but the incorrectly documented min/max are still confusing people and developers.

They should be documented as string and context explained in description.

Anyone else agree?

I have noticed this on quite a few routes.

In what way does min/max date params differ from fromdate/todate?

Edit

Actually when I look at it closer, the min/max say that they are context sensitive to the sort type.

How is a date min/max valid when sorting by, for instance votes?

Is this an oversight? I am assuming so when I change the tag to [bug].

Feel free to correct me if I am mistaken or missing something.

###Update: this is still not resolved.

It does not affect me but the incorrectly documented min/max are still confusing people and developers. They should be documented as string and context explained in description.

Anyone else agree?

I have noticed this on all sorted routes.

The min/max say that they are context sensitive to the sort type yet are documented as date.

How is a date min/max valid when sorting by, for instance votes?

###Update: this is still not resolved.

It does not affect me but the incorrectly documented min/max are still confusing people and developers. 

They should be documented as string and context explained in description.

Anyone else agree?