fix: add getOverrideProps to StorageManager

[bombguy]

Problem

The override props are not being applied to StorageManager

Solution

render spread attribute for getOverrideProps

Links

Ticket

GitHub issue : aws-amplify/amplify-studio#970

Automated tests

• Verified snapshot

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[reesscot]

Shouldn't it also be possible to override the wrapping Field component? I don't see an getOverrideProps call here:

      <Field
        errorMessage={errors.imgKeys?.errorMessage}
        hasError={errors.imgKeys?.hasError}
        label={\\"Images\\"}
        isRequired={false}
        isReadOnly={false}
      >

[bombguy]

Shouldn't it also be possible to override the wrapping Field component? I don't see an overrides call here:

      <Field
        errorMessage={errors.imgKeys?.errorMessage}
        hasError={errors.imgKeys?.hasError}
        label={\\"Images\\"}
        isRequired={false}
        isReadOnly={false}
      >

Yes, that is also possible as well. Should the overrideProps be spread in both Field & StorageManager?

[codecov-commenter]

Codecov Report

Merging #1020 (12c9020) into main (1fbf44d) will increase coverage by 0.00%.
The diff coverage is 100.00%.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

@@           Coverage Diff           @@
##             main    #1020   +/-   ##
=======================================
  Coverage   93.71%   93.72%           
=======================================
  Files         122      122           
  Lines        5428     5430    +2     
  Branches     1620     1620           
=======================================
+ Hits         5087     5089    +2     
  Misses        323      323           
  Partials       18       18           

Impacted Files	Coverage Δ
...s/codegen-ui-react/lib/react-component-renderer.ts	100.00% <100.00%> (ø)
...i-react/lib/utils/forms/storage-field-component.ts	96.61% <100.00%> (+0.05%)	⬆️

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1fbf44d...12c9020. Read the comment docs.

[Jshhhh]

Shouldn't it also be possible to override the wrapping Field component? I don't see an overrides call here:

      <Field
        errorMessage={errors.imgKeys?.errorMessage}
        hasError={errors.imgKeys?.hasError}
        label={\\"Images\\"}
        isRequired={false}
        isReadOnly={false}
      >

Yes, that is also possible as well. Should the overrideProps be spread in both Field & StorageManager?

Shouldn't it also be possible to override the wrapping Field component? I don't see an overrides call here:

      <Field
        errorMessage={errors.imgKeys?.errorMessage}
        hasError={errors.imgKeys?.hasError}
        label={\\"Images\\"}
        isRequired={false}
        isReadOnly={false}
      >

Yes, that is also possible as well. Should the overrideProps be spread in both Field & StorageManager?

I think the overrideProps should be one or the other, or have a different key passed into getOverrideProps

[bombguy]

The override props should only be applied to the StorageManager since the configuration is specific to the StorageManager, not Field component.

This pattern is used in other wrapper component we render. (e.g. ArrayField)