A wrapper as in: a second method which has named parameters, namely the ones which don't have a default value in the meta data.
So you generate (the wrapper):
ActionQuery.MySproc(string searchText)
and that method calls:
ActionQuery.MySproc(null,null,null,null,...x30,searchText,null,null,x20)
which is the one already generated. The wrapper is generated with an additional template. We currently don't support this so you have to write the template yourself. You can do this with an include template bound to the templateid 'Custom_ActionProceduresTemplate', so it's included when the action stored procedures are generated.
It's been a few years and I don't know exactly what David was referring at but I think it was this.
Now the problem: there's no meta-data available which says 'this parameter has a default vaule of 'NULL''. We use SELECT * FROM INFORMATION_SCHEMA.PARAMETERS on sqlserver to obtain the meta-data of parameters of a proc, but that doesn't report whether a parameter has a default value or is optional. SSMS uses SMO which parses the header of a proc, and with that can determine whether it has a default value, but we don't use that and there's no other way through the database.
So the only way is that you know the procs and parameters which are optional and mark them as such in the designer with the SP call. (check the 'Is Optional' checkbox). You can then use this info for the template. But as they're not DB sourced, if the signature changes, it won't update the sp call in the project.