You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It has come to my attention that several developers face challenges when attempting to create basic content type filters. This recurring issue suggests that there might be a gap in our documentation that leaves developers without clear guidance on this relatively straightforward task.
Mostly it was about developers not knowing about this possibility, failure the importance of using WhereInputQueryObjectType or need to register IIndexAliasProvider.
Proposed Solution:
To improve developer experience and address this problem, I propose we enhance our documentation. Specifically, I have drafted additional documentation focusing on guiding developers through the process of creating these filters step by step.
Call to Action:
I have submitted a pull request with the proposed documentation changes here: #16111
I welcome feedback on the PR and am open to suggestions on further improving the documentation to make this process as clear as possible for all our developers.
The text was updated successfully, but these errors were encountered:
We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).
This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.
Problem Description:
It has come to my attention that several developers face challenges when attempting to create basic content type filters. This recurring issue suggests that there might be a gap in our documentation that leaves developers without clear guidance on this relatively straightforward task.
Mostly it was about developers not knowing about this possibility, failure the importance of using WhereInputQueryObjectType or need to register IIndexAliasProvider.
Proposed Solution:
To improve developer experience and address this problem, I propose we enhance our documentation. Specifically, I have drafted additional documentation focusing on guiding developers through the process of creating these filters step by step.
Call to Action:
I have submitted a pull request with the proposed documentation changes here: #16111
I welcome feedback on the PR and am open to suggestions on further improving the documentation to make this process as clear as possible for all our developers.
The text was updated successfully, but these errors were encountered: