Skip to content

Comments

feat: React Native SDK update for version 0.24.0#88

Merged
abnegate merged 1 commit intomainfrom
dev
Feb 19, 2026
Merged

feat: React Native SDK update for version 0.24.0#88
abnegate merged 1 commit intomainfrom
dev

Conversation

@ChiragAgg5k
Copy link
Member

@ChiragAgg5k ChiragAgg5k commented Feb 19, 2026

This PR contains updates to the React Native SDK for version 0.24.0 .

@coderabbitai
Copy link

coderabbitai bot commented Feb 19, 2026

Walkthrough

This pull request updates the Appwrite SDK version from 0.23.1 to 0.24.0 across the package manifest and client SDK header. It introduces two new public static query builder methods to the Query class: containsAny and containsAll, which support matching array elements on attributes. The existing contains method documentation is clarified to specify its string substring matching behavior and to direct users toward the new methods for array attribute queries. All changes are additive with no modifications to existing functionality.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main changes: a version update to 0.24.0 across package.json, client header, and new Query methods in the React Native SDK.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch dev

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (2)
src/query.ts (2)

148-148: Optional: rename valuevalues to match the array-parameter convention in the class.

All other methods in Query that accept an array parameter use the plural name values (intersects, elemMatch, exists, notExists, select, distanceEqual, etc.). containsAny and containsAll use value (singular) for any[], creating an inconsistency.

♻️ Proposed rename
-  static containsAny = (attribute: string, value: any[]): string =>
-    new Query("containsAny", attribute, value).toString();
+  static containsAny = (attribute: string, values: any[]): string =>
+    new Query("containsAny", attribute, values).toString();
-  static containsAll = (attribute: string, value: any[]): string =>
-    new Query("containsAll", attribute, value).toString();
+  static containsAll = (attribute: string, values: any[]): string =>
+    new Query("containsAll", attribute, values).toString();

Also update the @param tags accordingly:

-   * `@param` {any[]} value
+   * `@param` {any[]} values

Also applies to: 160-160

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@src/query.ts` at line 148, Rename the array parameter name from value to
values in the static methods Query.containsAny and Query.containsAll to match
the class convention; update the method signatures and all internal references
from value → values and adjust the JSDoc `@param` tags to refer to values so
documentation and code stay consistent with other methods like intersects,
elemMatch, exists, notExists, select, and distanceEqual.

129-131: Optional: qualify {@link} references with the class name for reliable tooling resolution.

{@link containsAny} and {@link containsAll} are bare symbol references. Some documentation generators (TypeDoc, VS Code IntelliSense) resolve these more reliably when fully qualified as {@link Query.containsAny}.

♻️ Proposed fix
-   * Note: For array attributes, use {`@link` containsAny} or {`@link` containsAll} instead.
+   * Note: For array attributes, use {`@link` Query.containsAny} or {`@link` Query.containsAll} instead.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@src/query.ts` around lines 129 - 131, Update the JSDoc at the method
describing string/array attribute checks to fully qualify the referenced methods
so tooling can resolve them: replace the bare {`@link` containsAny} and {`@link`
containsAll} with {`@link` Query.containsAny} and {`@link` Query.containsAll} in the
comment near the string-attribute docs (the docblock mentioning "For array
attributes, use {`@link` containsAny} or {`@link` containsAll} instead.") so tools
like TypeDoc/IntelliSense can correctly link to the methods.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@src/query.ts`:
- Line 148: Rename the array parameter name from value to values in the static
methods Query.containsAny and Query.containsAll to match the class convention;
update the method signatures and all internal references from value → values and
adjust the JSDoc `@param` tags to refer to values so documentation and code stay
consistent with other methods like intersects, elemMatch, exists, notExists,
select, and distanceEqual.
- Around line 129-131: Update the JSDoc at the method describing string/array
attribute checks to fully qualify the referenced methods so tooling can resolve
them: replace the bare {`@link` containsAny} and {`@link` containsAll} with {`@link`
Query.containsAny} and {`@link` Query.containsAll} in the comment near the
string-attribute docs (the docblock mentioning "For array attributes, use {`@link`
containsAny} or {`@link` containsAll} instead.") so tools like
TypeDoc/IntelliSense can correctly link to the methods.

@abnegate abnegate merged commit 539821b into main Feb 19, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants