The first version has been implemented.
I will open specific issues for improvement.
Committed!
I'll release a new version of the module later today
Committed. Thanks!
lussoluca → made their first commit to this issue’s fork.
Committed. Thanks!
lussoluca → made their first commit to this issue’s fork.
Committed. Thanks!
Committed! Thanks
lussoluca → made their first commit to this issue’s fork.
Fixed (cspell too)
lussoluca → made their first commit to this issue’s fork.
lussoluca → created an issue.
lussoluca → created an issue.
lussoluca → created an issue.
lussoluca → made their first commit to this issue’s fork.
lussoluca → created an issue.
Thanks for your suggestion, I think that is a good addition to the readme. I've opened a MR; there's just a minor typo, then I can merge it
Probably, decorating the event_subscriber is no longer possible until 📌 Replace ContainerAwareEventDispatcher with Symfony EventDispatcher Fixed lands on Drupal 11 (required changes have been reverted in 🐛 Add BC layer for contrib modules using ContainerAwareEventDispatcher as a typehint (BC fix for #2909185) Fixed )
lussoluca → made their first commit to this issue’s fork.
A working patch has been committed in 📌 Use service decorators Needs review
A solution can be to add a new tab and save the schema metadata in a third-party setting of the backend configuration, but at this point, I think this is no longer a priority for the first release.
I've added a message to the "Fields" tab that warns the user to go to the "Processor" tab to complete the setup.
The patch is empty; in any case, the .ddev folder there because of https://github.com/ddev/ddev-drupal-contrib
It seems to be the same problem as 🐛 Circular reference detected for service "hook_event_dispatcher.module_handler" Active . I'm closing this as a duplicate and I'm committing a fix to the other issue.
Thanks
I've also added support for https://github.com/ddev/ddev-drupal-contrib to speed up local development
lussoluca → created an issue.
lussoluca → created an issue.
lussoluca → created an issue.
lussoluca → created an issue.
It seems related to Drush itself.
I have a custom Drush command with its drush.services.yml, and I have the error. If I delete the drush.services.yml file (and load required services using \Drupal::service(...)), it works.
lussoluca → created an issue.
lussoluca → created an issue.
Committed to 1.0.x-dev
lussoluca → made their first commit to this issue’s fork.
The latest version has added support to manage synonyms in the index config; this issue is no longer needed
SearchAPITypesenseBackend class has been heavily rewritten; this error no longer occurs in my tests.
Feel free to reopen the issue if you still have problems.
SearchAPITypesenseBackend class has been heavily rewritten; this error no longer occurs in my tests.
Feel free to reopen the issue if you still have problems.
The latest implementation uses the Guzzle client provided by Drupal, this is no more needed
Committed and pushed to 1.0.x-dev
lussoluca → made their first commit to this issue’s fork.
Good catch!
Committed to 1.0.x-dev
lussoluca → changed the visibility of the branch 3432853-add-support-for to active.
lussoluca → changed the visibility of the branch 3432853-add-support-for to hidden.
lussoluca → created an issue.
The latest dev version is compatible with both drupal 9 and drupal 10
Thanks for the idea, I've used it on 📌 Prepare for the first release Active .
I've temporary removed the Drush comand, I'll add it back soon.
Merged in
📌
Prepare for the first release
Active
.
Thanks!
Merged in
📌
Prepare for the first release
Active
.
Thanks!
lussoluca → created an issue.
I've already contacted them. What can be the next step? I try to contact them again?
I contacted both actual maintainers using the personal contact form of drupal.org and on the Drupal Association Slack workspace.
No one answered in about two months.
The project page is: https://www.drupal.org/project/search_api_typesense →
I've committed all my work here: https://github.com/lussoluca/typesense_drupal/tree/main/web/modules/cust..., but I can open a merge request on drupal.org if you prefer.
Thanks.
lussoluca → created an issue.
Merged, thanks!
Yes, we're working on it.
If you want, you can join us tomorrow at the Drupal Global Contribution Weekend ( https://www.drupal.org/community/events/drupal-global-contribution-weeke... → ); we'll also work on this module.
lussoluca → created an issue.
nicxvan → credited lussoluca → .
mikkmiggur are you using the hook_event_dispacther module as bob.hinrichs ?
Committed and pushed to 3.0.x
lussoluca → created an issue.
@paolo, all issues have been addressed
The actual patch fails with this error:
Fatal error: Uncaught TypeError: Drupal\Core\Config\ConfigFactory::__construct(): Argument #2 ($event_dispatcher) must be of type Symfony\Contracts\EventDispatcher\EventDispatcherInterface, Drupal\tracer\Controller\TraceableControllerResolver given, called in /var/www/html/web/core/lib/Drupal/Component/DependencyInje
ction/Container.php on line 259 and defined in /var/www/html/web/core/lib/Drupal/Core/Config/ConfigFactory.php:72 Yes, now it shold work. I'll tag a new release later this week
I've added a comment to the MR
lussoluca → created an issue.
Test added, let me know if it's ok
I can work on it.