Closed aazaff closed 8 years ago
Don't forget to file a separate age_rule issue for all other routes.
This is very low priority, as it is something that is readily accounted for in users of the API via whatever mechanism they wish.
It's just that using the age_bottom and age_top system implies that its going to be a constrained search, so I think it is misleading unless if you explain that we have some explicit system for this. At the very least the documentation should be updated to reflect how we are doing it.
Agreed re. documentation; can rarely have too much of that. But, it is a very constrained search. It is apparent in the return that Xbt, XbL, XFL, and XFt units are identified for the given age_bottom, age_top constraints.
I would like a parameter to make it so that searches will only return units constrained to be between age_bottom & age_top or interval_name.
Ideal format
https://macrostra.org/api/units?age_bottom=252&age_top=240&age_rule=within
https://macrostra.org/api/units?age_bottom=252&age_top=240&age_rule=all