Ignore location rules when adding fields to the schema. Fixes #52.

[peterjanes]

This hasn't obviously broken anything in my installation, but I haven't done exhaustive testing on it either.

[jasonbahl]

@peterjanes I believe this will cause that filter to always return true, regardless of using within WPGraphQL or not.

Can you describe what this solves so we can make sure we're not filtering too heavily?

[peterjanes]

You're right, it does show all of the fields all the time. I'll figure out how to detect whether it's a query in GraphQL, or move it to a more appropriate place. (My original branch name was issue-52-naive, which was apt.)

The goal is to show all ACF fields in the schema, even if they have a location rule that only displays them on an admin screen when a particular condition is met. For example, I have a number of field groups that are only displayed when a post's category is set to a specific value, and I want to be able to query them when I display that post.

[edit: just noticed that "fixes #52" in the description doesn't link to #52, so I'll do that here.]

[stephanedemotte]

+1 for this one,

With

  ->setLocation('post_type', '==', 'page')

It's ok.

But with

  ->setLocation('post_type', '==', 'page')
    ->and('page', '!=', $someID);

All my fields is never registered. We can't use the power of "set location"