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
I will add any typo functions I find here ongoing, if anymore.
These are functions that are just outdated or not updated into the documentation.
For example, I think all object functions are to be set_*() but not all are or are at least not all consistent with the documentation yet, or just missed with them all.
This one can have quite a few different methods to try, so ti took me a little and looking at the code to figure this one out.
To be more clear, the result will be the undefined method error. At least that is what I am getting on my end, until I call the correct one.
theperfectwill
changed the title
Function typos or documentation inconsistencies...
Issues: Function typos or documentation inconsistencies...
May 22, 2018
theperfectwill
changed the title
Issues: Function typos or documentation inconsistencies...
Issue: Function typos or documentation inconsistencies...
Aug 13, 2018
Hi.
I will add any typo functions I find here ongoing, if anymore.
These are functions that are just outdated or not updated into the documentation.
For example, I think all object functions are to be
set_*()
but not all are or are at least not all consistent with the documentation yet, or just missed with them all.set_field_width()
is actuallyset_width()
.input_type()
is actuallyset_input_type()
.Reference: https://www.ultimate-fields.com/docs/fields/complex/
The text was updated successfully, but these errors were encountered: