Refactor parentUserId logic in SearchModal to use effectiveParentId based on advanced state
This commit is contained in:
parent
fa97df0520
commit
f7fab195fd
@ -217,9 +217,11 @@ export default function SearchModal({
|
|||||||
setAddSuccess('')
|
setAddSuccess('')
|
||||||
setAdding(true)
|
setAdding(true)
|
||||||
try {
|
try {
|
||||||
|
// If advanced is not checked, or if advanced is checked but parentId is not set (root selected), use rootUserId as parentUserId
|
||||||
|
const effectiveParentId = (!advanced || !parentId) ? rootUserId : parentId;
|
||||||
const data = await addUserToMatrix({
|
const data = await addUserToMatrix({
|
||||||
childUserId: selected.userId,
|
childUserId: selected.userId,
|
||||||
parentUserId: advanced ? parentId : undefined,
|
parentUserId: effectiveParentId,
|
||||||
forceParentFallback: forceFallback,
|
forceParentFallback: forceFallback,
|
||||||
rootUserId,
|
rootUserId,
|
||||||
matrixId,
|
matrixId,
|
||||||
|
|||||||
Loading…
Reference in New Issue
Block a user