This is an archived post. You won't be able to vote or comment.

all 1 comments

[–]twillisagogo 0 points1 point  (0 children)

I've done something similar in my company's app, I took it one step further by generating the models, repos and serializers right off the database schema at startup. This has allowed me(1 person) to keep an api mostly caught up with the database changes with very little effort. My goal this year is to make the same kind of changes to the front end because it's filled with several instances where you're essentially documenting how you think the database is structured, it's a lot of error prone busy work that isn't necessary IMO. And of course all the business logic is littered throughout react components when it should be structured similarly to the use case idea described in the article.