Vaibhav 428700538a fix(studio): handle null db_pool when creating api schema (#41512) ...

Clicking "Create and expose schema to Data API" fails with error:


<img width="461" height="114" alt="image"
src="https://github.com/user-attachments/assets/0b37c443-2cba-4f4b-8535-c1143801dc72"
/>

The postgrest config can return `db_pool` as null,
but the mutation was passing it directly to the API which expects a
number.
This fix omits `db_pool` from the request body when null,
allowing it to use its default value.


- closes https://github.com/supabase/supabase/issues/41511


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Bug Fixes**
* Improved API settings configuration handling to properly manage
database pool parameters, ensuring more accurate and reliable API schema
mutations.

<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

2026-02-06 11:59:02 +00:00

..

create-and-expose-api-schema-mutation.ts

fix(studio): handle null db_pool when creating api schema (#41512)

2026-02-06 11:59:02 +00:00