Open dpagini opened 1 year ago
Tracking internally as BUGS-6172
@dpagini is the net result that you have to manually configure the module after installing it?
I actually created a support ticket for this about 2 weeks back, and posted on a few of the other issues, but it seems like none of those were getting traction... just in case it helps you cross-reference the support ticket.
The schema doesn't have much effect on the usage of the module, so no, I don't have to manually configure anything. My project has automated tests however, and they fail while this schema is invalid. I was using the patch I mentioned from post 7 on the d.o issue, but that doesnt apply anymore to the updated project once #165 was merged in.
Describe the bug This is described in more detail on the d.o issue that is still open and reported the same problem. This was attempted to be fixed in #101 and #165, but neither of those are providing a full schema. The patch posted in comment 7 on the drupal.org issue, I believe, is a more appropriate way to provide the schema for this module. The module does not appear to be providing any of its own properties, so you should just be able to extend the standard connector provided by
search_api_solr
. This will also ensure that this continues to work in the future if the main module adds any properties.To Reproduce Steps to reproduce the behavior:
search_api_pantheon
Expected behavior Automated testing should not flag an invalid schema.
Screenshots
Desktop (please complete the following information): Smartphone (please complete the following information): N/A
Additional context N/A