GeezerVison is showing github.com — [email protected] causes issues · Issue #2479 · angular-fullstack/generator-angular-fullstack
This repository was archived by the owner on Jul 29, 2026. It is now read-only.
This repository was archived by the owner on Jul 29, 2026. It is now read-only.
Description
- I understand that GitHub issues are not for tech support, but for questions specific to this generator, bug reports, and feature requests.
| Item |
Version |
| generator-angular-fullstack |
4.1.2 |
| Node |
4.5.0 |
| npm |
3.10.2 |
| Operating System |
Windows 10 |
| etc |
etc |
| Item |
Answer |
| Transpiler |
Babel / TypeScript |
| Markup |
HTML / Pug |
| CSS |
CSS / LESS / SCSS / Stylus |
| Router |
ngRoute / ui-router |
| Client Tests |
Jasmine / Mocha |
| DB |
MongoDB / SQL |
| Auth |
Y / N |
| etc |
etc |
Please be aware: the following event on thing.events.js does not work: Thing.schema.post(e, emitEvent(event));, since Thing.schema.post event is not triggered with [email protected] ActivityAwk34 commented on Jan 30, 2017 Are you sure there is a Mongoose issue here? I don't see anything breaking in the 4.8.0 changelog gordonaspin commented on Feb 3, 2017 +1 I had same problem with Thing.schema.post(e, emitEvent(event)) not emitting events in mongoose 4.8.1, downgraded to mongoose 4.7.7 and everything ok. Also, I would suggest adding ghostMode: false to the browsersync config in server/config/express.js as the default. Awk34 commented on Feb 3, 2017 Have either of you submitted a bug report to Mongoose yet? gordonaspin commented on Feb 3, 2017 I did not. I wasn’t sure it was mongoose at fault or not. I’m kind of new to fullstack and not confident I could pull together a stand-alone example of the event emitting not working.
…Awk34 commented on Feb 3, 2017 From reading this bug report, it seems like there might have been an unintended breaking API change in mongoose 4.8.0 EliKrumholz commented on Feb 5, 2017 EliKrumholz commented on Feb 7, 2017 From the Mongoose folks:
mutating the underlying schema after the Thing model has been created by mongoose.model() isn't a supported behavior. Make sure you define all your hooks before calling mongoose.model()
@ernisto has a solution in #2491 that does just that. alkiko commented on Feb 7, 2017 Awk34 commented on Feb 7, 2017 @ernisto do you thing you might submit a Pull Request for your fix? Climax777 commented on Feb 8, 2017 ernistkg commented on Feb 9, 2017 @Awk34 Yes it would be Great! But I need some time to create Pull Request according to rules and best practices. added a commit that references this issue on Feb 11, 2017This issue will close once commit e3ed67f is merged into the 'canary' branch.e3ed67f added 2 commits that reference this issue on May 13, 2017This issue will close once commit f69f560 is merged into the 'master' branch.f69f560 This issue will close once commit 79bdeed is merged into the 'master' branch.79bdeed
MetadataMetadataDevelopmentNo branches or pull requestsIssue actions
|