Drupal 11 compatibility and test coverage #4401
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Mark modules as Drupal 11 compatible, and add test coverage for Drupal 11.0.
Requires adding a GRANT PRIVILEGE command to database, need to make follow-up ticket(s) to make this less hack-y. Also makes a small change to the schema building logic in datastore, which did not actually account for the possibility of the
INT UNSIGNEDtype. Both of these are to deal with the change to mysql 8 including the ddev defaults, and aren't related to any actual D11 changes..Documentation updated to reflect these requirements.
Describe your changes
QA Steps
Checklist before requesting review
If any of these are left unchecked, please provide an explanation