Describe the proposed solution
Sylius/Sylius#11509
Sylius/Sylius#11510

Monofony version affected: 0.2.3 & 0.3.2

Description
I'm using the monofony bundle on a project that (I created july 2020) and since this friday (23/10), i have an error when using composer install.
It fails to install monofony/core (v0.2.3). It tries to dowload monofony/core from dist but the link leads to a 404 error. Then it tries to clone the commit, but the reference is gone (70778ec872c416cdbb7ef7debcd6e57bc920a2d5). Then I have a RuntimeException :

fatal: reference is not a tree: 70778ec872c416cdbb7ef7debcd6e57bc920a2d5

It does the same when I try to install a new project using the command composer create-project monofony/skeleton acme but this time, the commit reference is not the same (link to the dist):

fatal: reference is not a tree: f407dea88750df7c7711348511d240b77bb161ca

Steps to reproduce
Install a new monofony project using the command composer create-project monofony/skeleton acme

Monofony version affected: 0.4.0

Description

When clicking on add button on form type with a collection. The add button show a strange string.

Steps to reproduce

Add a CollectionType on a form.

Possible Solution

Copy/paste the change on Sylius ui bundle theme.html.twig on the monofony/admin-pack recipe.

Hello Monofony Team,

First of thanks for the great starter package for Symfony. This has great potential to be a de-facto tool for starting any Symfony application.

Some of the key concerns:

• Is it compatible with Symfony 5.x?
• Instead of re-inventing the wheel for API, why not to include API-Platform?

Monofony version affected: 0.4

Description
OAuth on Api Platform swagger is not configured.

Steps to reproduce
http://localhost:8000/api

Possible Solution

# config/packages/monofony_api.yaml
api_platform
    swagger:
        [..]
        api_keys:
            apiKey:
                name: Authorization
                type: header

Description
The folder public/assets is not in gitignore

Steps to reproduce
create a new project
run yarn build instead of yarn dev
git commit -m "first commit"

observe public/assets is being committed, although it shouldn't.

Possible Solution
add public/assets to gitignore

Steps to reproduce:

• search on google „monofony”
• open documentation https://monofony.readthedocs.io/en/latest/ or deprecated monofony repo
• ask yourself how to install this

what happens:

• you are a bit confused and left with a bad feeling about this

what should happen:

• you should see in the first page from docs the installation guideline

if approved, I can provide PR to fix this.

Monofony version affected: all

Description
"Doctrine\Common\EventSubscriber" has already been autoconfigured and merge
!! () does not support merging autoconfiguration for the same class/interface.

Steps to reproduce

Possible Solution
We have to check if it is already tagged or not.

Monofony version affected: all ?

Description

Errors are not visible on tab. We should have this:

Steps to reproduce

Possible Solution

Copy that changes into admin-pack recipes
https://raw.githubusercontent.com/Sylius/Sylius/102ff91f0b65932b0e828f66c9e24d449b41391b/src/Sylius/Bundle/AdminBundle/Resources/private/js/sylius-compound-form-errors.js

Describe the proposed solution
You create yourself an account. You fill in a big form. Now you get redirected to your email to confirm it. You close the app, go to your email, find the mail, open it, click the link, and you are redirected to a login form with a flash message that you can now safely login.

But you have to input again the username, the password. Cognitive load++.

Same for reset password: you go to the website, it asks you to login. You input your email and a password you remember, it's wrong. Try a couple of variants, end up with the same error - wrong password.

You decide to reset it. Then you go to reset password. Enter your email, sends you back to login with a flash message to check your email. Again: You close the app, go to your email, find the mail, open it, click the link, and you are redirected to a form where you can set the new password. You write it, twice and hit submit.

Back to login, with a flash message. Now you have to insert the username, again, and then the new password. Again. Cognitive load++. Rage++.

Solution

<?php

namespace App\EventSubscriber;


use Sylius\Bundle\UserBundle\Security\UserLoginInterface;
use Sylius\Bundle\UserBundle\UserEvents;
use Sylius\Component\User\Repository\UserRepositoryInterface;
use Symfony\Component\EventDispatcher\EventSubscriberInterface;
use Symfony\Component\EventDispatcher\GenericEvent;
use Webmozart\Assert\Assert;

class AutologinSubscriber implements EventSubscriberInterface
{
    /**
     * @var \App\Repository\UserRepository
     */
    private $userRepository;
    /**
     * @var \Sylius\Bundle\UserBundle\Security\UserLoginInterface
     */
    private $userLogin;
    /**
     * @var string
     */
    private $firewallContextName;

    public function __construct(
        UserRepositoryInterface $userRepository,
        UserLoginInterface $userLogin,
        string $firewallContextName
    ) {
        $this->userRepository = $userRepository;
        $this->userLogin = $userLogin;
        $this->firewallContextName = $firewallContextName;
    }

    /**
     * @return array|string[]
     */
    public static function getSubscribedEvents(): array
    {
        return [
            UserEvents::POST_PASSWORD_RESET => 'autoLogin',
        ];
    }

    public function autoLogin(GenericEvent $event)
    {
        $user = $event->getSubject();
        Assert::notNull($user);

        $user->setEnabled(true);
        $this->userRepository->add($user);

        $this->userLogin->login($user, $this->firewallContextName);
    }
}

    Sylius\Component\User\Repository\UserRepositoryInterface: '@sylius.repository.app_user'

    App\EventSubscriber\AutologinSubscriber:
        class: App\EventSubscriber\AutologinSubscriber
        arguments:
            $firewallContextName: '%firewall.app.context%'

--- a/config/packages/security.yaml
+++ b/config/packages/security.yaml
@@ -5,6 +5,9 @@ imports:
 
 parameters:
     secret: '%env(resolve:APP_SECRET)%'
+    firewall.app.context: 'app'
+    firewall.admin.context: 'admin'
+    firewall.api.context: 'api'
 
 security:
 
@@ -22,7 +25,7 @@ security:
 
     firewalls:
         admin:
-            context: admin
+            context: '%firewall.admin.context%'
             pattern: /admin(?:/.*)?$
             provider: sylius_admin_user_provider
             form_login:
@@ -54,10 +57,11 @@ security:
             fos_oauth: true
             stateless: true
             anonymous: true
+            context: '%firewall.api.context%'
 
         app:
             switch_user: true
-            context: app
+            context: '%firewall.app.context%'
             pattern: /.*
             provider: sylius_app_user_provider
             form_login:
diff --git a/config/routes/frontend/security.yaml b/config/routes/frontend/security.yaml
index 3465090..7f89171 100644
--- a/config/routes/frontend/security.yaml
+++ b/config/routes/frontend/security.yaml
@@ -49,7 +49,7 @@ app_frontend_password_reset:
         _controller: sylius.controller.app_user:resetPasswordAction
         _sylius:
             template: frontend/account/resetPassword.html.twig
-            redirect: app_frontend_login
+            redirect: app_frontend_homepage

The solution above is a PoC I implemented for my needs. It works for me. If you are interested, I can submit it in a PR to be included in Monofony by default and, maybe, why not, in Sylius as well.

Monofony version affected: 0.7.0

  [RuntimeException]                                                                                                                      
  Symfony pack "monofony/admin-pack" must duplicate all entries from "require-dev" into "require" but entry "behat/behat" was not found.  

Steps to reproduce:

export SYMFONY_ENDPOINT=https://flex.symfony.com/r/github.com/symfony/recipes-contrib/1022
composer create-project monofony/skeleton acme

Dependabot couldn't resolve your project's dependencies as it couldn't access Twig.

You can provide additional git credentials in your Dependabot dashboard by clicking into the account menu (in the top right) and selecting 'Config variables'. If you use a custom token for the host github.com make sure it has read access to this repo, too.

View the update logs.

Monofony version affected: dk

Description

https://demo.monofony.com/admin/bookings/38

detail booking lead to 500

Steps to reproduce
goto https://demo.monofony.com/admin/bookings/38

Possible Solution

Describe the proposed solution

Now, Behat suite configuration is on config/suites.yaml

To be clearer and more coherent, add a specific behat directory.

config/behat/suites.yaml
and move config/suites directory into config/behat/suites.

Dependabot couldn't resolve your project's dependencies as it couldn't access doctrine-bridge.

You can provide additional git credentials in your Dependabot dashboard by clicking into the account menu (in the top right) and selecting 'Config variables'. If you use a custom token for the host github.com make sure it has read access to this repo, too.

View the update logs.

Dependabot couldn't resolve your project's dependencies as it couldn't access process.

You can provide additional git credentials in your Dependabot dashboard by clicking into the account menu (in the top right) and selecting 'Config variables'. If you use a custom token for the host github.com make sure it has read access to this repo, too.

View the update logs.

Hello there!

My name is Ana. I noted that you use the mutation testing tool infection in the project.
I am a postdoctoral researcher at the University of Seville (Spain), and my colleagues and I are studying how mutation testing tools are used in practice. With this aim in mind, we have analysed over 3,500 public GitHub repositories using mutation testing tools, including yours! This work has recently been published in a journal paper available at https://link.springer.com/content/pdf/10.1007/s10664-022-10177-8.pdf.

To complete this study, we are asking for your help to understand better how mutation testing is used in practice, please! We would be extremely grateful if you could contribute to this study by answering a brief survey of 21 simple questions (no more than 6 minutes). This is the link to the questionnaire https://forms.gle/FvXNrimWAsJYC1zB9.

Drop me an e-mail if you have any questions or comments ([email protected]). Thank you very much in advance!!