Skip to content
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

invalid schema for search_api.server.pantheon_solr8.yml #168

Open
dpagini opened this issue Apr 24, 2023 · 2 comments
Open

invalid schema for search_api.server.pantheon_solr8.yml #168

dpagini opened this issue Apr 24, 2023 · 2 comments

Comments

@dpagini
Copy link

dpagini commented Apr 24, 2023

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.

plugin.plugin_configuration.search_api_solr_connector.pantheon:
  type: plugin.plugin_configuration.search_api_solr_connector.standard
  label: 'Search API Solr Pantheon connector settings'

To Reproduce
Steps to reproduce the behavior:

  1. Write an automated (functional) test that installs search_api_pantheon
  2. Run the automated test and observe the failure.

Expected behavior
Automated testing should not flag an invalid schema.

Screenshots
image

Desktop (please complete the following information):
Smartphone (please complete the following information):
N/A

Additional context
N/A

@namespacebrian
Copy link
Contributor

Tracking internally as BUGS-6172

@dpagini is the net result that you have to manually configure the module after installing it?

@dpagini
Copy link
Author

dpagini commented Apr 24, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants