-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
2.15.2 GA
-
None
-
False
-
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
-
-
Low
All parameters in the API are currently configured to accept empty values by default. This is causing issues with data validation and may lead to unexpected behavior. Parameters like `access_token`, `username`, `email`, and others should not accept empty values.
We need to investigate why this setting is enabled by default for all parameters. we want to ensure that this behavior is either disabled for all parameters across all APIs or at least for those that do not accept empty values. This will prevent invalid or incomplete data from being processed, improving the reliability of the API.