What are the Slack Archives?
Itβs a history of our time together in the Slack Community! Thereβs a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you wonβt be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
anyone knows where did `WebProfilerConstants` class go? it wasn't really marked deprecated, but then
Comments
-
spryker/webprofiler
was removed during your lastcomposer update
0 -
Had today the same.
0 -
do we know about the reason? π€
0 -
So either
composer require spryker/webprofiler
or I don't know.0 -
No, @UJN2JRU4F, such question doesn't bother me as I'm not a developer. π
0 -
π
0 -
well thing just wrecked my deploy, hence the question π it's still referenced in configs
0 -
i have a project i started on tuesday and it still contains the class. must be very recent
0 -
I'll ask internally then.
0 -
@UK5DS29L2 is it suite or b2c\b2b demoshops?
0 -
suite
0 -
ah
0 -
-
how did this impact you? π€
0 -
it blocks deployment
0 -
no i mean, how did he get suite changes into that project?
0 -
as it throws exception about missing class in configs
0 -
composer update?
0 -
it's not suite changes
it's just composer update0 -
@UK5DS29L2 Spryker docker env?
0 -
how old is the project?
0 -
no docker
0 -
by "how old" you mean when it was started?
0 -
https://github.com/spryker-shop/suite/blob/master/config/Shared/config_default-development.php#L34
considering this is still here, I don't think it matters0 -
well the core problem why it does not install that class is because we use composer.lock (that's why we have it, right?) and unless you do
composer update --dev
then there's no way to get the require-dev installed0 -
so we can either:
- start keeping two composer locks for each env
- disable webprofiler at all (because I'd rather have code tested on dev on same package set that I want to push on production later)
- stop moving things between require and require-dev without earlier notice about it's deprecation π
0 -
temporarily removed WebProfilerConstants from development config to make the deploy work
0 -
BUT I believe you should also update
https://github.com/spryker-shop/suite/blob/master/src/Pyz/Zed/Twig/TwigDependencyProvider.php
if it's only going to work in dev environment0 -
Not a beauty, but atm we are using
if (Environment::isDevelopment()) { $providers[] = new WebProfilerTwigLoaderPlugin(); }
as a workaround. So on staging production we don't have this dependency, so it won't get loaded0 -
but be aware its marked as deprecated now.
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 76 Spryker News
- 930 Developer Corner
- 788 Spryker Development
- 89 Spryker Dev Environment
- 362 Spryker Releases
- 3 Oryx frontend framework
- 35 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 26 Job Opportunities
- 3.2K π Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 70 Spryker Safari Questions
- 50 Random