Skip to content

Conversation

wouterj
Copy link
Member

@wouterj wouterj commented Dec 31, 2015

No description provided.

wouterj added a commit that referenced this pull request Dec 31, 2015
Allow FosJsRouting dev for Symfony 3
@wouterj wouterj merged commit 8c75a70 into master Dec 31, 2015
@wouterj wouterj deleted the fix_build branch December 31, 2015 13:39
@wouterj wouterj removed the wip/poc label Dec 31, 2015
@wouterj
Copy link
Member Author

wouterj commented Dec 31, 2015

Build is fixed again

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we require this or is it some other bundle that requires it? then the @dev should go in there rather than here, i think.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Testing requires it. @dev isn't needed, only to support Symfony 3 as a Symfony 3 supporting version has not been released.

However, as minimum stability is now set to stable for all CMF repositories, we need to explicitely allow FOSJsRoutingBundle to be installed in dev when needed.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay, i see. i hope to release this library really soon - should we do so with this line or should we try to tag a stable version of jsrouting?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah its only a dev dependency so no big deal!

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah and it's a dep that's not even used by this library. This is one of the problems of Testing 1.0, eventhough this is a component tested without framework integration, many bundles are still automatically loaded by Testing. For Testing 2.0, I would like to remove all config/required bundles from the component, so each library can make choices themselves.

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.

2 participants