Support CalDAV methods

According to your documentation, the methods contained in the CalDAV specifications (e.g. REPORT) are not included.

On your readme.md you claim:

Use Express-like routing syntax to capture outgoing requests.

However, express supports these routing methods: http://expressjs.com/en/5x/api.html#routing-methods

Are you interested in support them at at one point?

[TimDaub]

Examples of how I’m using REPORT:

• https://github.com/TimDaub/simple-caldav/blob/6d52cef9de24ac46c5c268a83cf4a2e1b616f40b/src/index.js#L98
• https://github.com/TimDaub/simple-caldav/blob/6d52cef9de24ac46c5c268a83cf4a2e1b616f40b/src/index.js#L172

As I’m proceeding to implement, more methods are potentially used… I will keep you posted.

[kettanaito]

to have an api that allows me to easily create my own namespace (for e.g. caldav)

There is such API, actually. It’s not documented yet, but you can create your own request handlers as long as they abide the request handler API. Here’s an example:

// src/mocks/handlers/caldav.js
import { restContext } from 'msw'

export function createCalDAVHandler(method) {
  return (mask, resolver) => {
    return {
      // Determine if a captured request is a CalDAV request.
      predicate(req) {
        const hasMatchingUrl = compareTwoUrls(req.url, mask)
        const hasSameMethod = req.method === method

        return hasSameMethod && hasMatchingUrl
      },

      // Define which functions are exposed in `ctx.*()`.
      // Here, let's return the same map of functions
      // that's used for `rest.*()` handlers.
      defineContext() {
        return restContext
      },

      // Pass response resolver as-is.
      resolver,
    }
  }
}

export const caldav = {
  report: createCalDAVHandler('REPORT')
}

Once defined, you can use that custom request handler:

import { setupWorker } from 'msw'
import { caldav } from './caldav'

const worker = setupWorker(
  caldav.report('/user', (req, res, ctx) => {...})
)

worker.start()

That is, basically, how such namespace would be implemented internally in MSW.

This is a bare example, and it may not be enough for complete usage, but it should give you an idea. I agree that this API needs to be refined and documented, and this is on the documentation improvement roadmap.

I’m thankful if you give it a try and share the insights with us!