fix: prevent sending full user object in participants search query - MEED-10198 - Meeds-io/meeds#4023#575
Merged
hakermi merged 1 commit intostable/7.1.x-exofrom Feb 17, 2026
Merged
Conversation
…EED-10198 - Meeds-io/meeds#4023 (#569) prior to this change, The participants suggester was not working when the current user had a long profile work experiences description. The issue was caused by sending the full `currentUser` object in the request query string, which resulted in an oversized and invalid query. This fix ensures that when space details are present, `currentUser` is sent as a boolean flag instead of the full object
|
Jihed525
approved these changes
Feb 17, 2026
This file contains hidden or 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
2 participants
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.
prior to this change, The participants suggester was not working when the current user had a long profile work experiences description. The issue was caused by sending the full
currentUserobject in the request query string, which resulted in an oversized and invalid query. This fix ensures that when space details are present,currentUseris sent as a boolean flag instead of the full object