I've read the design doc, nice!

I think we can't use Angular 2 if we're building a library.
But we can use TypeScript since it compiles to ES5.

I'm thinking it should be as lightweight as possible.
I'd go for building a flat design ourselves with Flexbox and CSS3 stuff.
That means dropping IE9 support, I don't think we should support it anyway.

In components/scenario-name.js > _isSelectedScenario > this.props.selectedScenarioId is always null

Working on it already...

Some browsers support more advanced features such as service workers which let us have greater control over HTTP requests.

Detect if service workers are available and apply the service workers strategy.
If this feature is not available then default back to XHR interceptors.

If we want an ability to enable multiple scenarios simultaneously, how to handle the situation if you have two enabled scenarios mocking the same url with different response? Both in API and UI.

Add support for using service workers instead of intercepting XHR requests.

When refreshing my app, BDSM opens.

Describe what bdsm is, why is it useful and show example screenshots.

Clicking on the import cloud does nothing

Investigate embedding the UI as an Iframe while still being able to communicate with the local API to capture requests and forward them to the UI.

Demos can include anything you like such as jquery, angular or react.

Ask the user if he wants to accept the changes, keep his or duplicate as another mocked rule/scenario.

Please remove the following message from the Dev Tools console, showing on app load:

bdsm.js:23 Download the React DevTools for a better development experience: https://fb.me/react-devtools

If you try a new scenario and click cancel when you're prompted for the name you create a new scenario with no name.

When opening the BDSM UI in the request history pane on the left add some helpful filtering for sorting by name, verb and status.

Search for all files with style= and use a class name instead.

Also...
Use the CSS classes for the method names instead of in the JS
Were already added in _vars.scss and _helpers.scss, just need to use a className instead of hard coding.

When I run my app in a new port (i.e. 8081 instead of 8080) the mocks are not available. Thanks :)

When request is fired, show the request in captured requests with a spinner

• Request/response headers
• Parameters (query/form-data)

And generally add more help text in the ui

For example if I run ThetaRay, and Tradency, and each one has its own mocks, they should be scoped to the application name.

This should be optional, i.e. if you don't specify app name it will all reside on 'default' scope - just to make it easier for newbies to start using BDSM.

TypeError: requestParams[key].match is not a function in bdsm/lib/api/interceptor.js

The code:

  checkParamsEquality(requestBody, responseParams) {
    const requestParams = UrlUtils.parseRequestBody(requestBody);
    const parameters    = Object.keys(requestParams);

    for (let key of parameters) {
      const regex = responseParams[key] ? new RegExp(responseParams[key]) : null;

      if (regex && !requestParams[key].match(regex)) {
        return false;
      }
    }

    return true;
  }

requestBody:
"{"AccountID":21431,"StartTime":"2015-11-01T00:00:00"}"

responseParams:
{ AccountID: 21431 }

I fails because requestParams[key] is a number value and not a string.

@morsdyce @ilyagelman
I had a really hard time understanding what this function does, and it's still a puzzle why do we need the RegExp.
Why not save the request body on the mock and compare them as is?
If it's not an option, am I to assume this function should compare 2 objects?
Perhaps it's a good time to add Lodash.

We should have only unique requests to avoid this:

Improve XHR interceptor logic to activate the correct set of rules needed to run at that point of time.

If a scenario is active it should go over all the mocked requests associated to the scenario and get the active mocked requests for that scenario.

If mocked requests is active go over all the mocked requests and get the active mocked requests.

only active mocked requests must intercept XHR requests, all other requests must pass through.

When creating a new mock and saving it, the dropdown doesn't update immediately. You need to close BDSM and open it in order to choose the new mock.

Refactor the UI toggle to be a react element and render it in the page context (separate from the main UI).

In order to increase maintainability.

It fails when trying to load uuid module.

ERROR in /Users/alex/Web Dev/Node/shredderjs/lib/api/models/rule.ts
(2,18): error TS2307: Cannot find module 'uuid'.

Ref:
microsoft/TypeScript#2709

Also, Object.assign does not work in IE, so we should polyfill it, though I'm not sure how to get Typescript to eat that.
microsoft/TypeScript#3889

e.g: JSON, CORS, NO-CACHE

Ref:
https://www.npmjs.com/policies/disputes

Current holder:
https://www.npmjs.com/package/bdsm

Note: Please check if this affects dead code elimination when bundling an app with bdsm in production mode

Add support for JSONP requests. This is most likely only achievable using service workers and will only be available for supporting browsers

Currently when deleting a scenario there is no confirmation asking you if you really want to delete it which is bad because the delete button could be clicked by mistake (or by a cat on your keyboard).

Add a confirmation modal that checks if you really want to delete this resource.

Implement or use an existing solution that allows to register callbacks when data changes.

Currently editing parameters for POST/PUT/DELETE are not available in the UI and not tested