Closed jacklinke closed 7 months ago
Please let me know thoughts on this, and I'll add tests and the associated test models with different pk types.
Uh nice. Would you try adding test models for these use cases?
This has been fixed in fb2bf46a01c4fb814d135956cbc1d6146b2272fb. I figured, you don't need to have specific field types for a Filter Input field.
When initializing the form, look at whether the related model field is a UUIDField, CharField, or other, and utilize forms.UUIDField, forms.CharField, or forms.IntegerField, respectively.
Should resolve #67 and replace PR #74 with a much simpler approach (no duplication of forms, which would be a breaking change).