Responsibility delegationįorm libraries tend to ask a developer to manage so many things that the one forgets about using a library at all. I cannot stress more on how devastating an obscure declaration is to the code you write. Today I see fields declared as Objects, or even worse, proving that this point is as valid as never.ĭeclaration of a form and its fields must be simple. Obscure declarationīack in the day we needed to create an array of strings, which would represent the fields, and pass it to the high-order component before the form is even mounted. The bottom line is, if a third-party solution results into you creating abstractions over it, then, probably, it never solved your problems in the first place. Especially when you wish to end up in the hell of non-maintainable abstractions. Our team hates writing boilerplate, so we couldn’t tolerate with providing blocks of configuration to high-order components around each form, or obscurely defining which fields a form will have before it renders. ![]() My emphasis here is that those can rather be handled on a form’s level, dramatically improving developer’s experience. Each of the points below can be dealt with to a certain extent.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |