fix(2999): add error validation to prevent objects in query params

[melmathari]

Prevent Objects in Query Parameters

Problem

Previously, the system allowed objects to be used in HTTP query parameters through the @http directive, which could lead to unexpected behavior since query parameters should only contain scalar values.

Solution

Added validation to ensure that query parameters only accept scalar values and not objects. The validation:

• Checks for object access in mustache templates (e.g., {{.args.criteria.field}})
• Provides clear error messages when objects are used
• Maintains compatibility with existing scalar query parameters

Changes

1. Added validate_query_params() method to the Http directive to check query parameter types
2. Added unit tests to verify validation logic
3. Added integration tests to verify end-to-end behavior

Example

graphql ❌ This will now fail validation

query {
findEmployees(criteria: { maritalStatus: MARRIED }) @http(
query: [{ key: "nested", value: "{{.args.criteria}}" }]
)
}

✅ This will work (using scalar)

query {
findEmployeesByStatus(status: MARRIED) @http(
query: [{ key: "status", value: "{{.args.status}}" }]
)
}

Testing

• Unit tests verify the validation logic for both valid and invalid cases
• Integration tests ensure proper error messages and end-to-end functionality
• All tests run automatically with the test suite

Error Message

When an object is used in a query parameter, users will receive a clear error:

/claim #2999

[melmathari]

@tusharmath Could you please review this pull request when you have a moment? Thank you for your contributions!

[tusharmath]

Hey @nocodeventure-nl! Thank you for your contribution to Tailcall 🙏

Unfortunately, we cannot merge this PR as the changes proposed do not align with the requirements in the linked issue. I encourage you to review #2999 once again and open a new PR with the required changes.

Thank you for your understanding 🙌