Closed (fixed)
Project:
Elasticsearch Helper
Version:
8.x-6.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
13 Feb 2020 at 09:33 UTC
Updated:
5 Jan 2023 at 15:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
eiriksmComment #3
imiksuAccording to my drupal-check run I found following errors:
Comment #4
sahana _n commentedPlease review the patch.
Comment #5
mitrpaka commentedThanks for the patches. Here is updated patch with some additions to previous ones.
Checked with https://www.drupal.org/project/upgrade_status - No known issues found.
Comment #6
mitrpaka commentedUpdated patch.
Comment #7
fastangel commentedI tried the last patch and is getting problem with drupal 9 install with:
Drupal\Core\Extension\InfoParserException: The 'core_version_requirement' can not be used to specify compatibility for a specific [error]
version before 8.7.7
I attach the patch with the fix.
Comment #8
jcnventuraComment #9
mradcliffeThis isn't necessary to add to the info.yml file if the core_version_requirement is also ^8.7.7 || ^9. Removing core: 8.x and adding core_version_requirement: ^8.7.7 || ^9 is enough to make the requirement on Drupal core. The system module is a mandatory core module that is always installed.
This seems odd to me, but I guess if that's the pattern that's being used to separate versions in this contrib module that's okay.
However it should be core_version_requirement: ^8.8 || ^9 without the patch version as documented on specifying the core_version_requirement when needed.
If this is ever called, there will be an error thrown because the entityManager property doesn't exist? Unless it exists on the base class?
If we want to use this pattern then we should add a protected $deprecatedProperties array similar to the core class of the same name.
Otherwise this will throw an exception because $deprecatedProperties property doesn't exist on this class.
Comment #10
jcnventuraAlso, makes no sense to specify 8.7.7, as that is the minimum version that support core_version_requirement. Might be better to just state
^8 || ^9. However, seeing that part of the module requires 8.8.0, and as we can't have multiple composer.json files, I think this module must declare the following in all the .info.yml files:^8.8 || ^9Comment #11
ridhimaabrol24 commentedComment #12
ridhimaabrol24 commentedPatch #7 failed to apply on the latest branch. Fixed the issues and implemented suggestion from #9 and #10. Providing interdiff as well for clarity.
Comment #13
jcnventuraALL modules must have core_version_requirement except the one belonging to the 'Testing' package.
Comment #14
mitrpaka commentedMaybe we should add note to README.md that prior to 8.8 version there is need to use earlier dev version of the module as entity_get_display() was moved to EntityDisplayRepositoryInterface in 8.8.x (https://www.drupal.org/node/2835616)
Comment #15
jcnventuraThere's still a use of @entity.manager in elasticsearch_helper/examples/elasticsearch_helper_example/elasticsearch_helper_example.services.yml
Comment #16
mrinalini9 commentedComment #17
mrinalini9 commentedUpdated patch as per the changes mentioned in #15, please review.
Comment #19
jcnventura