![]() ![]() Your code will still run if you violate them, but violations should be rare and well-justified. These rules have been found to improve readability and/or developer experience in most projects. Exceptions may exist, but should be very rare and only be made by those with expert knowledge of both JavaScript and Redux. These rules help prevent errors, so learn and abide by them at all costs. We've divided these rules into three categories: Priority A: Essential You are encouraged to follow these recommendations, but take the time to evaluate your own situation and decide if they fit your needs.įinally, we'd like to thank the Vue documentation authors for writing the Vue Style Guide page, which was the inspiration for this page. We also understand that team preferences vary and different projects have different requirements, so no style guide will fit all sizes. With that in mind, we've put together this list of recommendations to help you avoid errors, bikeshedding, and anti-patterns. In addition, many developers have asked us to provide official guidance to reduce decision fatigue. However, time and experience have shown that for some topics, certain approaches work better than others. There are many ways to use Redux, and much of the time there is no single "right" way to do things. It lists our recommended patterns, best practices, and suggested approaches for writing Redux applications.īoth the Redux core library and most of the Redux documentation are unopinionated. ![]() This is the official style guide for writing Redux code. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |