ACF Field JavaScript API about acf HOT 2 OPEN

If I am understanding this correctly, #2 getInput(), getControl() also return jQuery elements, correct? If the are, the examples are a little inconsistent, which is what threw me off. If that is the case, I like idea #3 because you know they're jQuery and it seems more performant to only query when necessary, however you said performance is negligible.

But I also feel like I'm missing something. What is something like field.search = function(){}; supposed to return in #1?

When you say return a JS type instead of jQuery element, is there a JS object representing a field or do you mean returning an HTML${n}Element?

from acf.

Hi @tikitariki

Thanks for the reply and feedback. You raised some great points, and I'll address them below:

Point 1

If I am understanding this correctly, #2 getInput(), getControl() also return jQuery elements, correct?

Yes. I've just updated the examples to better reflect this.

Point 2

I like idea #3 because you know they're jQuery and it seems more performant to only query when necessary, however you said performance is negligible.

I'm leaning towards this idea too. It optimizes performance by only querying when needed, but also allows these functions to become dynamic and even allow for parameters.

Point 3

What is something like field.search = function(){}; supposed to return in #1?

This was an example to demonstrate how naming conventions are important. All functions that start with a $ symbolize those that return a jQuery element, nothing else.

Point 4

When you say return a JS type instead of jQuery element, is there a JS object representing a field or do you mean returning an HTML${n}Element?

Here I am talking about the differentiation between a jQuery object and any other JS type. The getX functions should return a JS type (string, int, object, array, etc) where as the findX functions should return a jQuery object.

from acf.