You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at parking_rates and sqft_per_rate among other params emerges the following question:
Why if parcel_sizes can use imperial and metric measure units the other parameters are fixed to the former? Maybe units could be considered imperial if not specified (default) and metric if some flag param exists.
Maybe not a top priority but could we consider this mainly to be able to use ProForma module outside countries that use imperial system.
The text was updated successfully, but these errors were encountered:
I saw that note but the acceptable ranges are defined for feets and all
methods names and comments use _feet_ or _sqft_. If this method is
measuring system agnostic maybe could be named `squareUnitProForma()` or
something as generic as it is.
Anyway, I think is no more than a narrow semantic difference. Maybe we
should resume this discussion later, when more significant issues are
solved.
Looking at
parking_rates
andsqft_per_rate
among other params emerges the following question:Why if
parcel_sizes
can use imperial and metric measure units the other parameters are fixed to the former? Maybe units could be considered imperial if not specified (default) and metric if some flag param exists.Maybe not a top priority but could we consider this mainly to be able to use ProForma module outside countries that use imperial system.
The text was updated successfully, but these errors were encountered: