I'll get to work on changing at least "New Project" to add a database row
today.

Keeping the HTTP headers would stop you from getting the actual error
message wouldn't it, since you're passing back a JSON object? We can get
rid of those headers if it means more meaningful errors passed back to the
client application.

There's not much to any of the database request files. It all boils down to
the SQLiteProjectSerializer being created and calling the appropriate
method from that. If that's too much we could move the creation to
connect.php, it's light enough to not be a bother and most (currently all,
I think) things calling connect use this anyway. The rest is just the input
checks and such.


On Sat, Feb 1, 2014 at 4:40 PM, seanblue <notifications@github.com> wrote:

> In PHP/CommonMethods.php:
>
> > @@ -37,4 +37,16 @@ function projectExists($projectName) {
> >      return is_dir("projects/" . $projectName);
> >  }
> >
> > +/**
> > + * Returns all existing projects.
> > + */
> > +function getExistingsProjects() {
> > +    function filter($var) {
> > +        return (strpos($var, ".") !== 0);
> > +    }
> > +
> > +    $projects = scandir("projects/");
>
> Also, I don't think I'll be doing any more work this weekend. So try to do
> everything you can without me making changes.
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/KSHSK/WAVED/pull/57/files#r9367364>
> .
>