APi explorer components

[eileenmcnaughton]

Hi @colemanw - per the issue I pinged you from I am trying to build a form re-using a portion of the apiv4 explorer code.

I suspect that solving this in my use case could open up a lot of options.

My use case is pretty simple - basically I want to be able to select the criteria for a contact.get api call in angular. The end result is just a url.

I got it working but grabbing the latest code I find it regressed because I was relying on
scope.operators = CRM.vars.api4.operators;

and I guess those are now not assigned as aggressively due to changes in the apiv4 code.

I also ruthlessly copied the make widget stuff

SO I wonder what a method would be to make those 2 things from the apiv4 explorer code re-usable outside the apiv4 explorer

[colemanw]

and I guess those are now not assigned as aggressively due to changes in the apiv4 code.

The api4 explorer used to reside on the "main" CiviCRM angular page of civicrm/a but that page is getting pretty crowded so @totten's current recommendation for extensions is to create their own base page for their Angular routes.

I also ruthlessly copied the make widget stuff

That's also received some updates recently, FYI.