You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, our schemas are controlled by our back-end team.
To come up with a controlled approach from their side they suggested building a prototype that includes all possible available attributes for all types (with default values ).
On the front side, we have the following concerns:
Passing attributes that are related to one type to another type might cause unexpected behaviors for (example select specific attributes to toggle or text field etc )
The size of JSON for each field might be huge (maybe over 100 200 attribute ? ) which 90% is not used will cause unneeded load on the page leading to performance issues on vue form itself and the page generally
debugging issues due to the size the JSON passed
having multiple forms on the page contributing to adding additional performance issues and load on the page
I need a feedback about those concerns if those would be valid issues or not and if any other issues could be introduced due to such approach
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently, our schemas are controlled by our back-end team.
To come up with a controlled approach from their side they suggested building a prototype that includes all possible available attributes for all types (with default values ).
On the front side, we have the following concerns:
I need a feedback about those concerns if those would be valid issues or not and if any other issues could be introduced due to such approach
Beta Was this translation helpful? Give feedback.
All reactions