fix: Incorrect onChange value when an unloaded value is pasted into AsyncSelect

[michael-s-molina]

SUMMARY

Fixes a bug where the onChange event was being fired with an incorrect value when pasting a text that corresponds to an existing option in the database, which was not loaded previously due to pagination.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

Screen.Recording.2024-04-11.at.15.24.01.mov

Screen.Recording.2024-04-11.at.15.23.18.mov

TESTING INSTRUCTIONS

1 - Use an async select that has enough values to trigger pagination. You can also reduce the Select's default page size to test.
2 - Paste a value that is not loaded yet by the Select component
3 - Check that the onChange event is called with the correct value. It's easier to check this when the options have numeric values. In that case, onChange should receive the numeric value instead of the pasted text as the value property.

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[kgabryje]

LGTM