One thing I noticed while looking at the source code for core was
while attempting to rewrite certain functions, there were issues with
passing arguments in the correct order. Specifically, I was having
issues while rewriting showForm() .. have you guys looked into passing
optional arguments as associative arrays or passing them via a
container object? I feel as though this would allow developers to
better use the API without needing switch statements for each object
type they're attempting to call. (Orthogonality?)

Zipp

_______________________________________________
Glpi-dev mailing list
[email protected]
https://mail.gna.org/listinfo/glpi-dev

Reply via email to