documentation VS explicit-design

Have you heard about Feature-Sliced Design? I have personally found it extremely helpful as the project grows larger, though it can have a bit of a learning curve

In our case, the current folder structure resembles Feature-Sliced Design:

Feature-slice design is the one and only correct solution imho

(https://feature-sliced.design/)

for large spa I recommend https://feature-sliced.design/

There are many more benefits of using feature sliced design which are well documented in the docs. I highly recommend you to check it out and learn new ways of organizing your frontend project.

Hi, I use feature-sliced design for big or middle spa. Excellent solution for scalability! https://feature-sliced.design/

Ссылка на офф сайт.

You can also see a way around this restriction in "DDD, Hexagonal, Onion, Clean, CQRS, ... How I put it all together" and Feature Sliced.

If you have ideas that could complement this list, create an issue in the project repository. I’d be happy to discuss! 👋

If desired, this hook itself can also be decoupled from specific implementations such as useStoreWriter, useStoreReader, and useConverter. I won't go into detail about this in the text, but I'll leave a link to an example where I describe different ways of composing the use case in hooks.

Source code on GitHub

Source code for the current step on GitHub

By the way, source code for this series is available on GitHub. Give the repo a star if you like the posts!

Perhaps the benefits would be more visible in a larger application, but I decided that a simple converter would be sufficient for the experiment. If you have any ideas on how to improve this, please, open an issue or PR on GitHub. Let's discuss it! 👋

Next, we will try to design a converter and describe its model in terms of types and functions. You can find the final result and source code for all examples in this post on GitHub.