@aws-amplify/data-schema 1.25.4 → 1.25.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@aws-amplify/data-schema",
3
- "version": "1.25.4",
3
+ "version": "1.25.6",
4
4
  "license": "Apache-2.0",
5
5
  "repository": {
6
6
  "type": "git",
@@ -774,9 +774,7 @@ function calculateAuth(authorization: Authorization<any, any, any>[]) {
774
774
  }
775
775
 
776
776
  if (rule.provider) {
777
- // identityPool maps to iam in the transform
778
- const provider = rule.provider === 'identityPool' ? 'iam' : rule.provider;
779
- ruleParts.push(`provider: ${provider}`);
777
+ ruleParts.push(`provider: ${rule.provider}`);
780
778
  }
781
779
 
782
780
  if (rule.operations) {
@@ -142,5 +142,11 @@ export type ModelPrimaryCompositeKeyInput<
142
142
  ge?: SkIr;
143
143
  gt?: SkIr;
144
144
  between?: [SkIr, SkIr];
145
- beginsWith?: SkIr;
145
+ // `beginsWith` accepts a partial because the underlying AppSync VTL builds
146
+ // the `begins_with` prefix by skipping null fields. Requiring all fields
147
+ // (as the other operators do) forces callers to pass empty strings for
148
+ // trailing fields, which the VTL then appends as `#` delimiters — yielding
149
+ // a malformed prefix on 3+ field composite sort keys. Allowing partial
150
+ // input lets callers express "all rows under this leading prefix".
151
+ beginsWith?: Partial<SkIr>;
146
152
  };