8000 Make sure that mixins are specific to each new app by daffl · Pull Request #104 · feathersjs/feathers · GitHub
[go: up one dir, main page]

Skip to content

Make sure that mixins are specific to each new app#104

Merged
daffl merged 1 commit intomasterfrom
unique-mixins
Feb 4, 2015
Merged

Make sure that mixins are specific to each new app#104
daffl merged 1 commit intomasterfrom
unique-mixins

Conversation

@daffl
Copy link
Member
@daffl daffl commented Feb 4, 2015

This pull request fixes a bug that caused weird issues. The reason was that an applications mixins array was shared through every Feathers application.

@daffl daffl mentioned this pull request Feb 4, 2015
@daffl
Copy link
Member Author
daffl commented Feb 4, 2015

Looks like this depends on #105 - which has to be merged first - for the tests to pass.

daffl added a commit that referenced this pull request Feb 4, 2015
Make sure that mixins are specific to each new app
@daffl daffl merged commit 611c63a into master Feb 4, 2015
@daffl daffl deleted the unique-mixins branch February 4, 2015 03:48
daffl pushed a commit that referenced this pull request Aug 29, 2018
* chore(package): update ws to version 6.0.0

* Update Travis installatino script
daffl pushed a commit that referenced this pull request Aug 29, 2018
* chore(package): update ws to version 6.0.0

* Update Travis installatino script
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0