'added' event is not emited until child has access to stage

[fireveined]

Description

Now we wait with emiting 'added' event until child has access to stage, to ensure it will be mediated.

Related Issue

#67

Motivation and Context

In our project we build views from bottom to top, so none of them were mediated.

How Has This Been Tested?

Tested in use case from linked issue and in our project.

Types of changes

• Updated docs / Refactor code / Added a tests case (non-breaking change)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

[tiagoschenkel]

@fireveined, please take a look at the failing travis log.

This message is everywhere:

Module not found: Error: Can't resolve 'pixi.js' in '/home/travis/build/RobotlegsJS/RobotlegsJS-Pixi/src/robotlegs/bender/extensions/contextView/pixiPatch'

Unfortunately the peerDependency doesn't work as expected since yarn is being used to manage the dependencies. And, as far as I'm concerned, even the npm package manager is not solving properly the peer dependencies. When a peer dependency is added, the binaries are not downloaded when running yarn install or npm install so this is why the job is failing. Remember that the travis integration build runs on a fresh environmnt so everything is wiped out before. Locally it could work but is because the node_modules folder was not cleaned.

Would be possible to revert your last commit?

Regarding the version of the pixi.js library, I think that makes sense to accept a more broad version range, like ^4.0.0. I prefer to use this notation instead the 4.x notation, since both ways are semantically correct and will produce the same result (you can check this here).

But in any case, I would prefer to change the version range of the dependencies in another issue/pull request. Currently I don't know exactly how the this plugin is used, nor how often one development team is updating the pixi.js dependency on each project. Would be good to discuss this in a separate topic.

[tiagoschenkel]

Would be good to update also the CHANGELOG.md file located in the root of this project.

Please add one line describing briefly the changes made in the changelog, then a reference to this pull request and to the issue being closed.

You can add an entry line here.

[tiagoschenkel]

Problem related to peerDependencies solved. Accepting other changes.

[tiagoschenkel]

#72 extends the concept to removed event.