Filter should be provided in options hash when calling ActiveRelationResource.count

The filters are passed in from the processor as the first parameter in ActiveRelationResource.count. However they are not in the options hash, so if the custom records method relies on those they will not be available. From Gitter

This issue is a (choose one):

• Problem/bug report.
• Feature request.
• Request for support. Note: Please try to avoid submitting issues for support requests. Use Gitter instead.

Checklist before submitting:

• I've searched for an existing issue.
• I've asked my question on Gitter and have not received a satisfactory answer.
• I've included a complete bug report template. This step helps us and allows us to see the bug without trying to reproduce the problem from your description. It helps you because you will frequently detect if it's a problem specific to your project.
• The feature I'm asking for is compliant with the JSON:API spec.

Description

Choose one section below and delete the other:

Bug reports:

Please review Did you find a bug? and replace this content with a brief summary of your issue. If you can't submit a bug report template please be as thorough as possible when describing your your description. It's helpful to indicate which version of ruby and the JR gem you are using.

Features:

Please replace this line with a clear writeup of your feature request. Features that break compliance with the JSON:API spec will probably be closed.

Beginne damit, den Prozessorpfad nachzuverfolgen, der ActiveRelationResource.count aufruft, und untersuche anschließend, wie dessen benutzerdefinierte records-Methode den ersten Parameter und den options-Hash erhält. Prüfe die relevanten count- und records-Tests und betrachte das Issue als erledigt, wenn die an count übergebenen Filter über den options-Hash verfügbar sind, ohne bestehendes Verhalten zu beeinträchtigen.