You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When copying arrays, can just use [[NSArray alloc] initWithArray:existingArray copyItems:YES] instead of doing it by hand.
Erroring out on empty paths for subscribe makes sense, but for read should just respond with empty array. That would match the behavior of actually sending the corresponding requests to the server.
The text was updated successfully, but these errors were encountered:
1) Use initWithArray:copyItems:YES when copying arrays, instead of hand-rolling
the copy.
2) For read, empty paths should just lead to an empty result, not an error, just
like they would if the read actually happened.
Fixesproject-chip#26169
1) Use initWithArray:copyItems:YES when copying arrays, instead of hand-rolling
the copy.
2) For read, empty paths should just lead to an empty result, not an error, just
like they would if the read actually happened.
Fixesproject-chip#26169
1) Use initWithArray:copyItems:YES when copying arrays, instead of hand-rolling
the copy.
2) For read, empty paths should just lead to an empty result, not an error, just
like they would if the read actually happened.
Fixesproject-chip#26169
1) Use initWithArray:copyItems:YES when copying arrays, instead of hand-rolling
the copy.
2) For read, empty paths should just lead to an empty result, not an error, just
like they would if the read actually happened.
Fixes#26169
[[NSArray alloc] initWithArray:existingArray copyItems:YES]
instead of doing it by hand.The text was updated successfully, but these errors were encountered: