-
Notifications
You must be signed in to change notification settings - Fork 158
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
OP-320: Add possibility to select section type and fill up collection of items of this type #500
Conversation
jkindly
commented
Jun 19, 2024
Q | A |
---|---|
Bug fix? | no |
New feature? | yes |
BC breaks? | no |
Deprecations? | no |
Related tickets | OP-320, OP-312 |
License | MIT |
… of items of this type
@@ -25,7 +25,7 @@ | |||
|
|||
<field name="publishAt" column="publish_at" type="datetime_immutable" nullable="true"/> | |||
|
|||
<many-to-many field="sections" target-entity="BitBag\SyliusCmsPlugin\Entity\SectionInterface"> | |||
<many-to-many field="collections" target-entity="BitBag\SyliusCmsPlugin\Entity\CollectionInterface"> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How doctrine would behave with changing the field name, when we have a table with data? Isn't it safer to use the "sections" column name in all mapping places? The field can stay then as "collections".
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It doesn't change anything in the database. It is only related to the $collections field in entity, but in the database we have join-column-name: section_id
Co-authored-by: Marcin Kukliński <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are still some unresolved comments 🖖