The idea is that for each resource we want to dispaly in a grid, there will be one endpoint for data and another for metadata.
The metadata endpoint will bascially return a list of columns and their types based on the POJO being displayed.

From one point of view, I can see the productivity gain with this approach. However, a lot of team members are against this approach because it is a strong coupling.

I feel that this is just repeating a mantra.

I am arguing that any frontend web app is coupled with its backend, we are not developing a generic web app that can be plugged and played with any existing backend so why is a stronger coupling withour backend is a bad idea?

So is this approach a bad idea from a software design perspective  ?

The idea is that for each resource we want to dispaly in a grid, there will be one endpoint for data and another for metadata.
The metadata endpoint will bascially return a list of columns and their types based on the POJO being displayed.

From one point of view, I can see the productivity gain with this approach. However, a lot of team members are against this approach because it is a strong coupling.

I feel that this is just repeating a mantra.

I am arguing that any frontend web app is coupled with its backend, we are not developing a generic web app that can be plugged and played with any existing backend so why is a stronger coupling with our backend a bad idea?

Is this approach a bad idea from a software design perspective?