aglinxinyuan commented on PR #4138: URL: https://github.com/apache/texera/pull/4138#issuecomment-3695356372
> @aglinxinyuan I do prefer a `fields` parameter in case in the future we want to return other user information to the frontend. We already have several endpoints that return additional user information. This endpoint lives under the workflow sub-URL and is intended to be used only for workflow-related resources. If we decide to unify all user-related endpoints in the future, it may be helpful to first review and align the existing user-related URLs. Introducing a fields parameter here could be interpreted as exposing database-level details to the frontend, which ideally should not need to be aware of individual fields. Additionally, hardcoding field names as strings may increase the risk of the frontend and backend becoming out of sync over time. Would it be reasonable to defer adding this parameter until there is a concrete use case that requires it? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
