bug: field.Strings not generating as expected

[HaackTheSystem]

🌧 Describe the problem

When adding FilterGroupEqual and FilterGroupArray annotations to a Strings field, the query params are not getting added to the list endpoint.

⛅ Expected behavior

When adding either filter category above, I would expect to be able to have an includes or equals option for the Strings field like with other field types, but it doesn't seem to generate that option.

🔄 Minimal reproduction

No response

💠 Version: entrest

v1.0.2

🖥 Version: Operating system

linux/ubuntu

⚙ Additional context

No response

🤝 Requirements

• I believe the problem I'm facing is a bug, and is not intended behavior. Post here if you're not sure.
• I have confirmed that someone else has not submitted a similar bug report.

[lrstanley]

So, I thought this was just a bug in entrest, but looks like Ent doesn't generate predicates by default for JSON fields, which field.Strings() is under the hood (since not all db engines support native arrays like this): https://entgo.io/docs/predicates/#json-predicates

I think for basic things like Strings and Ints, I can use the sqljson package to craft these automatically on the entrest side, though I am still unsure of what the limitations are, currently. I will have to explore options.