Join GitHub today
add comments regarding FieldtypeDecimal #130
I really like what you did there, but would tackle it a bit differently. Instead of promoting the decimal fieldtype directly we need to inform the user about all the potential backdraws floats have first. Only after that's done the user can make an informed decision and this is where we can link to the decimal fieldtype.
Currently I don't feel like a user not aware of the difference between floats and decimals could make much sense about why this is there without doing the work and clicking all the links.
I also don't feel like the note is needed in that place. Why and how floats work differently then one might expect can be part of external information we link to. Important is that we warn about the issues of floats, explanation can happen elsewhere.
Totally agree, I wanted to make a first step :) I'm not well versed with benefits and drawbacks of those fieldtypes, so I'd happy to read someone's explanations. Maybe this would be a good reason for a dedicated blog post. They'll be part of the docs in the near future, so it would definitely make sense. Then we could just link to that blogpost (as official and compact resource) from all related Fieldtypes with a comment (int, float, decimal).