Issue #136: Missing implementation of core_userlist_provider #1
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.
Fix for Missing Implementation of core_userlist_provider and Metadata Test Failures
Issue KQMATH#136: Missing Implementation of core_userlist_provider
The Privacy API provider class for mod_jazzquiz did not implement the core_userlist_provider interface, causing unit test failures.
Added the required methods:
get_users_in_context(userlist $userlist)
delete_data_for_users(userlist $userlist)
These methods now correctly handle user data associated with the plugin's context.
Fix for Metadata Test Failures
Another test failure was identified related to missing metadata for the jazzquiz_attendance table.
The table jazzquiz_attendance contains the userid field, which was not declared in the get_metadata() method of the Privacy API provider.
Metadata for this table has been added, ensuring compliance with Privacy API requirements.