Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Allow schema caching per server when using a common base schema #1224
base: 8.x-4.x
Are you sure you want to change the base?
Allow schema caching per server when using a common base schema #1224
Changes from 5 commits
c7a38e0
d99470d
bed2473
5ae3f29
b7d1f4c
0368ccf
8d1a98d
112fcf8
48c0b44
88c8e6c
2ec7f03
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Instead of using a setter to configure the server ID, I'm wondering if it wouldn't be better to make the plugin configurable by implementing
ConfigurableInterface
. In fact, both schema plugins we ship are already configurable (but the base classSdlSchemaPluginBase
isn't, and changing this would be a B/C break).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.
This assumes that the setter has always been called, but it might not have been, and
$this->serverId
might beNULL
.Probably using a setter is not the best approach. Since the server ID is required for the plugin to work in the current it is essential that the setter is always called. The setter is not part of the
SchemaPluginInterface
and it also should not be, since it is not essential for all schema plugins, only for the ones that use caching.Maybe we can add a
server_name
key to the standard plugin configuration and check that this is populated in the plugin constructor? That would also enable us to gracefully introduce this change. We can emit a deprecation warning if it is missing.