Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecated ResourceManager Completely #6439

Merged
merged 16 commits into from
Mar 2, 2017
Merged

Conversation

CarsonF
Copy link
Member

@CarsonF CarsonF commented Mar 2, 2017

This removes the remaining usages of ResourceManager and adds a ton of deprecation notices.

I know this is late to be in 3.3. This would be best grouped in this release, because PathResolver has been added and ResourceManager has had most of its usage removed and deprecated.


The only other notable change in this PR is 1b19486. The theme filesystem is added to filesystem service at boot, instead of when the object is created. This allows the filesystem service to be accessed whenever, without fear of an infinite loop. The Twig loader was also changed to add the theme path at boot since it now doesn't exist before that point.

Copy link
Contributor

@GwendolenLynch GwendolenLynch left a comment

Choose a reason for hiding this comment

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

:shipit:

CarsonF and others added 16 commits March 2, 2017 16:55
…ning twig files for translations.

Yes I just said this shouldn't be done. It will be removed with translation refactor in 3.4.
…ead of with ResourceManager setup. I still hate this check, the config file is supposed to be optional.
…pending on them.

This allows us to call "filesystem" whenever we want without fear of infinite loop.
Merged other filesystem DI keys back into main filesystem key.

The theme path is also added to Twig loader at boot now as well to match and reset
its internal error cache if some dummy tries to render a theme template before boot.
…d of ResourceManager.

Yes, this adds side effects...will be scrapped with Config refactor soon.
…ocal adapter / mocks. Also asserting package names.
…. "view" was before "bolt_assets" which meant "view" value was ignored.
@GwendolenLynch
Copy link
Contributor

GwendolenLynch commented Mar 2, 2017

Before merging this, I would like to extend a very public "thank you" to @rossriley who originally authored ReourceManager.

ReourceManager was a transitional concept that he invested a lot of time and hard work in to get Bolt into a more flexible position starting with Bolt 2.0-dev, moving Bolt away from using hard coded file system paths … and a lot of people would not grasp exactly how far it took this project.

Bolt has grown as a platform considerably since then, and for quite a while now RM has needed to be replaced for a bunch of reasons that do not matter past "we want to make Bolt better, more powerful, and more flexible."

The functionality introduced in this PR marks the end of an era in a way, so 🍻 for all

@GwendolenLynch GwendolenLynch merged commit 60a3747 into bolt:release/3.3 Mar 2, 2017
@GwendolenLynch GwendolenLynch deleted the rm-fire branch March 2, 2017 05:09
@GwendolenLynch GwendolenLynch added this to the Bolt 3.3 - Feature release milestone Mar 17, 2017
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.

None yet

2 participants