Version 1.1.0 of can-fixture just got published.

This version is covered by your current version range and after updating it in your project the build failed.

can-fixture is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

• can get a message and send one back
• can simulate a basic RESTful-ish socket connection using can.fixture.store.

The dependency can-fixture was updated from 3.0.3 to 3.0.4.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

can-fixture is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

We need an option to turn off the noise in the console:

Some sort of configuration or something

The onFeathers link didn't get setup properly:

Version 2.1.3 of feathers just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As feathers is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

The latest version on npm doesn't have the connected and disconnected properties.

Check why demo is not working http://canjs.com/doc/can-fixture-socket.html

There is a disconnect event on normal socket.io socket objects.

Version 3.10.19 of can-util was just published.

This version is covered by your current version range and after updating it in your project the build failed.

can-util is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Version 1.3.0 of can-set just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As can-set is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

docs should show up in can-ecosystem

Version 1.7.4 of socket.io-client just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As socket.io-client is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

I think tests are failing because the Firefox version is not specified.

Version 3.6.2 of can-util just got published.

This version is covered by your current version range and after updating it in your project the build failed.

can-util is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

With AJAX fixtures, I only have to mock the services I want - everything else falls through to an actual AJAX request to the server. I would expect the same with sockets, but that is not the case.

Creating the mock server (and nothing else - no event listeners) prevents all socket messages from falling through to the "actual" socket connection to my server.

var io = require("socket.io-client");
var fixtureSocket = require("can-fixture-socket");
var mockServer = new fixtureSocket.Server(io);

If I set up event listeners, I am able to successfully mock a service with fixture data:

mockServer.onFeathersService('/users', store);

However, as it stands right now, I would need to do this for all of my services. I only want to do it for a select few services (like I can with AJAX).

Version 3.8.2 of can-util just got published.

This version is covered by your current version range and after updating it in your project the build failed.

can-util is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 1.3.0 of steal-tools just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As steal-tools is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Similar to canjs/can-stream#3. Show what each method name, what it's arguments are, what it returns, possibly an example of its use.

.Server(io)

Create a mocked SocketIO server. Intercepts SocketIO and overrides io.Manager.prototype to work with the mocked server.
This is the main method to fixture socket.io

var io = require('socket.io-client');
var mockServer = new fixtureSocket.Server(io);

mockServer.on('connection', function(){
    mockServer.emit('notifications', {test: 'OK'})
});

.toFixtureStoreHandler(fixtureStoreMethod)

Wrap fixture.store methods to become socket event handlers:

var fixtureStore = fixture.store([
    {id: 1, title: 'One'},
    {id: 2, title: 'Two'}
], new canSet.Algebra({}));

mockServer.on({
    'messages get': fixtureSocket.toFixtureStoreHandler(fixtureStore.getData)
});

.wrapFixtureStore(fixtureStore)

Wrap fixture store to provide socket event ready methods:

var socketMessagesStore = fixtureSocket.wrapFixtureStore(fixtureStore);

mockServer.on({
    'messages remove': socketMessagesStore.destroyData,
    'messages create': socketMessagesStore.createData,
    'messages update': socketMessagesStore.updateData
});

.connectFeathersStoreToServer(serviceName, fixtureStore, mockServer, [options])

Wrap fixture.store to implement FeathersJS protocol:

var fixtureStore = fixture.store([
    {id: 1, title: 'One'},
    {id: 2, title: 'Two'}
], new canSet.Algebra({}));

fixtureSocket.connectFeathersStoreToServer('messages', fixtureStore, mockServer);

Options can be used to specify id property name:

var fixtureStore = fixture.store([
    {_id: 1, title: 'One'},
    {_id: 2, title: 'Two'}
], new canSet.Algebra(canSet.props.id('_id')));

fixtureSocket.connectFeathersStoreToServer('messages', fixtureStore, mockServer, {id: "_id"});

This is only an issue I've noticed on Safari for Mac. Returning an error like this example results in an error Attempted to assign to readonly property.

var errors = require('feathers-errors');

mockServer.on('accounts::find', function (query, callback) {
  if (isAuthenticated) {
    fixtureSocket.requestHandlerToListener(accountStore.getList).apply(null, arguments);
  } else {
    var error = new errors.NotAuthenticated('not-authenticated');
    callback(error);
  }
});

It's also returning the same error with a plain JS error:

mockServer.on('accounts::find', function (query, callback) {
  if (isAuthenticated) {
    fixtureSocket.requestHandlerToListener(accountStore.getList).apply(null, arguments);
  } else {
    var error = new Error('not-authenticated');
    callback(error);
  }
});

If I return a plain JS object instead of an Error object, it works fine:

mockServer.on('accounts::find', function (query, callback) {
  if (isAuthenticated) {
    fixtureSocket.requestHandlerToListener(accountStore.getList).apply(null, arguments);
  } else {
    var error = {
      "name": "NotAuthenticated",
      "message": "not-authenticated",
      "code": 401,
      "className": "not-authenticated",
      "errors": {}
    };
    callback(error);
  }
});

console.log breaks IE9 if the console is not open.

Version 1.5.1 of steal just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As steal is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

After upgrading the packages to the latest of featherjs, the tests for feathers socketio are now failing.

I upgraded the devDependencies as follows:

"devDependencies": {
    "@feathersjs/feathers": "^3.3.1",
    "@feathersjs/socketio-client": "^1.2.1",
    "can-set-legacy": "<2.0.0",
    "detect-cyclic-packages": "^1.1.0",
    "done-serve": "^1.2.0",
    "donejs-cli": "^1.0.1",
    "es6-promise-polyfill": "^1.2.0",
    "generator-donejs": "^1.0.5",
    "jshint": "^2.9.1",
    "object-assign": "^4.1.0",
    "socket.io-client": "^2.2.0",
    "steal": "^1.5.6",
    "steal-qunit": "^1.0.1",
    "steal-tools": "^1.1.2",
    "testee": "^0.9.0"
  }

Then in the test.js file I removed the feathers-hooks package as this is no longer an external dependency:

...
var feathers = require('@feathersjs/feathers');
var feathersSocketio = require('@feathersjs/socketio-client');
...

var app = feathers()
  .configure(feathersSocketio(socket));
...

After making these changes and re-running the tests I see this error "Timeout of 5000ms exceeded calling find on messages".

Version 1.0.6 of generator-donejs just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As generator-donejs is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

We should be able to simulate a complete feathers socket.io service layer with can.fixture.store.