FullTextSearchFilter with propertyName specified throws exception from Contenful

[dibble-james]

Using FullTextSearchFilter without specifying a propertyName parameter seems to work but if use something like new FullTextSearchFilter(query, "fields.field") I'm getting a ContenfulException and an error detail of No field with apiName "field\[match\]" found.

[dibble-james]

I also get similar issues when using the NumericEquality enumeration

[ryan-codingintrigue]

Thanks for this. I've taken a look at the PR and can't think of a reason those backslashes are in there off the top of my head. I am currently without my development machine right now, but once I get it back I'll get this PR merged.

I tend to agree that none of the filters should have backslashes in there.