-
Notifications
You must be signed in to change notification settings - Fork 19
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
Introduce 4.0 compatibility #68
base: master
Are you sure you want to change the base?
Conversation
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.
Good start! Some comments:
- you'd better use
git move
to move files, it would be easier to track which files were simply moved and which ones were actually created/deleted - please remove all commented
use
statements, it will improve readability - please do not commit permission changes, the file permissions should be
644
, except for executable ones - And more importantly, please update the tests 🙂
@@ -13,5 +12,5 @@ final class ExtendedAttributeTypes | |||
{ | |||
const TEXT_COLLECTION = 'pim_catalog_text_collection'; | |||
|
|||
const BACKEND_TYPE_TEXT_COLLECTION = 'textCollection'; | |||
const BACKEND_TYPE_TEXT_COLLECTION = 'text_collection'; |
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.
Why did you change the backend type?
'wildcard' => [ | ||
$attributePath => '*' . $value . '*', |
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.
I'm not sure a wildcard query will work with an array field
{ | ||
public function createWithoutCheckingData(Attribute $attribute, ?string $channelCode, ?string $localeCode, $data): ValueInterface | ||
{ | ||
sort($data); |
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.
why do you want to sort the data here?
I'll try to answer your |
As I would like to revive this extension, this PR introduces compatibility with Akeneo 4.0.
This PR is intentionally a draft as there are a few todos that require feedback and in general, I would like to know if I am on the right track.
In the current state, the extension is installable, a new attribute of type "Text Collection" can be created and used. Interaction with the attribute is working (adding/deleting/sorting) and changes are persisted.
Open todos:
values
key is empty.pim_extended_attribute_type.denormalizer.flat.text_collection
class still needed?