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
Usually you have multiple tables in a database or multiple entities in doctrine. Currently, I have to write for each entity an extra ExtDirect controller with create, read, update and delete methods and @direct... annotations.
If you could support "call metadata", I could send the required tablename or entityname as metadata together with the Ext Direct call. On the server side I could write a single ExtDirect dispatcher and/or a generic CRUD service, resulting in lesser boilerplate code and code duplication.
Thanks.
The text was updated successfully, but these errors were encountered:
@middlebrain Can you elaborate the usage of the metadata configuration and the concept of call metadata a little bit? To be honest, I haven't used that yet and I didn't even know that this exists.
@middlebrain OK, just read the documentation and it's somehow clear now. How would you'd like to use that feature on PHP side? How would you expect to define the metadata at your PHP method?
See http://docs.sencha.com/extjs/6.0.2-classic/guides/backend_connectors/direct/specification.html#backend_connectors-_-direct-_-specification_-_call_metadata
Usually you have multiple tables in a database or multiple entities in doctrine. Currently, I have to write for each entity an extra ExtDirect controller with create, read, update and delete methods and @direct... annotations.
If you could support "call metadata", I could send the required tablename or entityname as metadata together with the Ext Direct call. On the server side I could write a single ExtDirect dispatcher and/or a generic CRUD service, resulting in lesser boilerplate code and code duplication.
Thanks.
The text was updated successfully, but these errors were encountered: