Workflow about zubr

[nkkollaw]

As I understand some of the functions will be just passing arguments to the wrapped functions without any change?

Yes, we're "guaranteeing" that all functions follow the rules set in our guidelines, but if core PHP functions already do, we're simply calling them without intervening in any way.

Second question - should we put functions under core NS? It would make sense if we'd like to add wrappers for extensions (eg php\mysql\connect / php\mysql\mysql_connect)?

IMHO, neither php\mysql\connect nor php\mysql\mysql_connect. I think that for a developer whose been using MySQL functions like mysql_query, mysql_connect the best, most intuitive thing would be to find their equivalents in \phpsane\mysql_query and \phpsane\mysql_connect.

Good idea. Also it would be good to add those issues to the milestone.

Yup, I'm adding all functions and then I'll edit them all at once. Saves time :-)

[radmen]

We would have to support all functions under "Core"

As I understand some of the functions will be just passing arguments to the wrapped functions without any change?

Second question - should we put functions under core NS? It would make sense if we'd like to add wrappers for extensions (eg php\mysql\connect / php\mysql\mysql_connect)?

I'm adding each function as an issue, so that whoever implements it can reference the issue while committing or doing pull requests.

Good idea. Also it would be good to add those issues to the milestone.

I think we should do 1 function per commit/request, referencing the issue.

+1

[nkkollaw]

Closing this as workflow is pretty clear by now.