I couldn't find a single scenario where I was using the Validate class in my
site level code. Dropped the overhead of calling a static class method multiple
times on a page by moving the logic in the Resource class. Also changed the
response to always return the errors as parameter => array. This allows a
developer to choose if they want to display one error or all of the errors.
Seems pointless to have class that had a single method that basically contained
all of the shit that the resource already had and knew. Moved respond() method
to the response class and moved all of the response validation logic and errors
from the router to the response class.
Validation logic was existing but it was reworked to abstract out checking for
required fields initially and then sanity checks after the fact. Filters are
applied before validation but after checking existence. No support for _PUT and
_DELETE at the moment as those do not exist as super globals natively in PHP.
Pretty sure we don't need it anymore. Could come back up in the future when an
API is returning URIs for static assets and they are being cached and it's not
being flushed correctly.
Been moving away from using this functionality in favor of either Grunt or
Gulp. Dropped functionality for minification of CSS and JS but left the dynamic
reference logic intact. This will be moved to the HTML class eventually and
expanded to support the generation of the HTML tags as well as injecting the
URI with a timestamp.
Thinking this may bork the test suite because it won't be able to fine ayah.
This is just part of the move towards having a local copy of pickles in the
project installed and managed by composer. Also retabbed the composer json.
There's no point in defining version numbers prematurely. I'll update with
exact versions as the need arises. At the moment `dev-master` outta be good
enough.
