Gareth Ari Aye
Gareth Ari Aye
We have this fancy interface https://github.com/mikedeboer/jsDAV/blob/master/lib/CalDAV/interfaces/iBackend.js, but AFAICT we don't have any "backends" which implement it. For my purposes, an in-memory backend would work for testing.
- Fixes #103 - Fixes #104 by configuring jshint and adding make task - Fixes #105 by specifying node
[CalDAVTester](https://trac.calendarserver.org/wiki/CalDAVTester) is a popular tool amongst folks at [CalConnect](http://calconnect.org/) to test the compliance of their caldav server implementations.
We have a couple example, "standalone" servers using jsDAV in `examples/` and it would be nice to add one that does calendaring.
npm ERR! [email protected] install: `node-gyp rebuild` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] install script. npm ERR! This is most likely a problem with...
There's a lot of code here! We could really benefit from a tool like [jshint](http://www.jshint.com/) to enforce consistent code style.
There are a lot of different kinds of things that live in `test/`. Many of them look like they run on mocha. Some look like they don't use programmatic assertions...
A short `README` file explaining the directory structure of the caldav subdirectory, the different components, and how they relate to the stuff in `shared/` and also `DAV/` would be very...