Skip to content

[Feature] Guide about doctrine naming_strategy #95

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

Open
vasilvestre opened this issue Mar 13, 2024 · 1 comment
Open

[Feature] Guide about doctrine naming_strategy #95

vasilvestre opened this issue Mar 13, 2024 · 1 comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@vasilvestre
Copy link
Contributor

vasilvestre commented Mar 13, 2024

Is your feature request related to a problem? Please describe.
When I install the project, with the naming strategy doctrine.orm.naming_strategy.underscore the fields are not found due to other case being used than underscore.

Unknown column 's0_.cron_expression' in 'field list'

Describe the solution you'd like
I'm not sure what the fix should be but a note about this would be great.

@oallain
Copy link
Member

oallain commented Mar 22, 2025

Yes,

We haven't specified the field names.
For example :

    #[ORM\Column(type: Types::STRING)]
    private string $cronExpression = '* * * * *';

The doctrine.orm.naming_strategy.underscore configuration is not the default configuration in Sylius (which is a shame, by the way).

I think we should specify the field names in the Plugin, because it's a shame to have to migrate the project for this.

@oallain oallain added good first issue Good for newcomers help wanted Extra attention is needed labels Mar 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants