[austin-cheney]

You are going about this all wrong.

The front end should know nothing about the back end and the back end should know nothing about the front end. They are separate systems running independently on separate computers.

What you are doing is called tight coupling. https://cleancommit.io/blog/whats-the-difference-between-tig...

You want the flexibility to do anything you want with your data and simultaneously do anything you want with your front end. That means you can generate any queries you want against any shape of data you want without making any changes to the front end. Likewise, you want the ability to make any changes to the content that is displayed to the user and the ability for the user to interact with that content no matter what is happening with the data.

I was laid off from a project with tight coupling, exactly as you envision, last year and it was horrible. Clearly, that tightly coupled project was intentionally designed with tight coupling in mind because the people making those decisions were supremely insecure in their ability to write logic for the front end. They had no idea what they were doing, everything was scary, and just wished the front end logic auto-magically reflected the database world where they found comfort. If that is you then its rough times ahead.