Skip to content
This repository has been archived by the owner on Jul 1, 2024. It is now read-only.

Make it compatible with symfony 5 #2

Open
GalloisLuca opened this issue Jul 23, 2021 · 16 comments
Open

Make it compatible with symfony 5 #2

GalloisLuca opened this issue Jul 23, 2021 · 16 comments

Comments

@GalloisLuca
Copy link

Description
The plugin is not compatible with symfony 5

Example
!! The service "workouse_availability_notifier_plugin.controller.availability_
!! notifier" has a dependency on a non-existent service "templating". Did you
!! mean one of these: "sylius.templating.helper.convert_money", "sylius.templa
!! ting.helper.adjustment", "sylius.templating.helper.format_money", "sylius.t
!! emplating.helper.currency", "sylius.templating.helper.locale", "sylius.temp
!! lating.helper.inventory", "sylius.templating.helper.product_variants_prices
!! ", "sylius.templating.helper.price", "sylius.templating.helper.variant_reso
!! lver", "sylius.templating.helper.checkout_steps", "sylius.templating.helper
!! .grid", "sylius.templating.helper.bulk_action_grid", "sonata.block.templati
!! ng.helper", "liip_imagine.templating.filter_extension"?

@chadyred
Copy link

Any news about it ?

@delirehberi
Copy link
Member

there is not active an development on that. we are open for prs.

@reyostallenberg
Copy link

Are you still open for PRs on that? I could and would like to help!

@delirehberi
Copy link
Member

yes, we would like to review and merge.

@reyostallenberg
Copy link

reyostallenberg commented May 3, 2022 via email

@delirehberi
Copy link
Member

delirehberi commented May 3, 2022 via email

@delirehberi
Copy link
Member

@reyostallenberg tag v1.0.0 created.

@chadyred
Copy link

chadyred commented May 8, 2022

Well done ^^

@reyostallenberg
Copy link

@delirehberi do you agree we should only fix for supported versions.

That will mean:

  • PHP 7.4/8.0/8.1
  • Symfony 4.4/5.4/6.0
  • Sylius 1.10/1.11 (as those fit the requirements above)

@delirehberi
Copy link
Member

delirehberi commented May 10, 2022 via email

@reyostallenberg
Copy link

Is it possible to get the scrutinizer config in the repo, so I can fix it for current situation?
It'll mean the config done in the interface of scrutinizer should be deleted and should be added to the root of the repo in a yaml file

delirehberi added a commit that referenced this issue May 17, 2022
scrutinizer config added to repo #2
@delirehberi
Copy link
Member

I sent a commit to master, is that ok?

@reyostallenberg
Copy link

That's okay

@costa-jeremy
Copy link

Hello,

It's possible to accept the PR pls ?

Thank you in advance

@delirehberi
Copy link
Member

@costa-jeremy it will be merged after pr is completed. still seems work in progress.

@reyostallenberg
Copy link

I'll take a look in this shortly. I'm sorry for the delay

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants