feat(authorization): skip undefined/empty query parameter

[hassan254-prog]

Describe the problem and your solution

• Some providers like Dropbox sign OAuth, do not allow empty query parameters, such as scope which we automatically inject.
• This PR introduces a flag authorization_url_skip_undefined that can be set to true for providers where we want to omit these undefined parameters from the authorization URL.

---

This PR introduces a new boolean configuration flag, authorization_url_skip_empty, to provider definitions, enabling selective omission of query parameters with empty or undefined values from OAuth authorization URLs. The update addresses cases where some providers (e.g., Dropbox Sign) reject URLs containing such parameters (like scope) when they're empty, enhancing compatibility with strict provider requirements.

Key Changes:
• Added authorization_url_skip_empty?: boolean to provider type definitions (provider.ts)
• Extended provider JSON schema (schema.json) to include the new flag
• Updated OAuth controller logic (oauth.controller.ts) to remove empty string query parameters from the authorization URL when the flag is enabled

Affected Areas:
• OAuth controller logic
• Provider configuration schema validation
• Provider TypeScript interface definitions

This summary was automatically generated by @propel-code-bot

[linear]

EXT-714 Nango does not support complete removal of `scope` params

[bodinsamuel]

Is there any risk to always remove them?

[hassan254-prog]

Is there any risk to always remove them?

I was thinking about that, but I’m concerned it might be a breaking change for some. What do you think, should we omit empty query params entirely for all?

[bodinsamuel]

I was thinking about that, but I’m concerned it might be a breaking change for some. What do you think, should we omit empty query params entirely for all?

I guess it could be 😞 lets go with that then 👍🏻

[TBonnin]

can we always skip the empty params? regarless of the provider and then avoid having to add yet another option to provider.yaml?

[bodinsamuel]

can we always skip the empty params? regarless of the provider and then avoid having to add yet another option to provider.yaml?

asked the same but in retrospect I'm sure some are relying on this unfortunately