Add new action to register custom Elementor endpoints

[gerardreches]

Prerequisites

• I have searched for similar feature requests in both open and closed discussions and cannot find an existing request.
• I have verified that the feature is still missing from the latest stable versions of Elementor or Elementor Pro.

What problem is your feature request going to solve? Please describe..

Elementor's regex for their global colors and typography endpoints don't allow hyphens or underscores in the global property ID, as they are currently randomly generated strings (check #12571 ). This makes difficult for advanced users with CSS knowledge to reuse the global color variables.

I am developing a solution to use user-defined IDs instead of random strings, which is already working and doesn't cause any issues with Elementor.

However, the implementation could be much better if I could make use of Elementor's existing classes. The requested action hook is necessary in order to extend the existing endpoint classes and correctly register them in the Controller. This would reduce the amount of code required to implement the feature, as most of it is copied from the existing class contained in the Elementor plugin, as well as improving compatibility and avoiding breaking changes.

Describe the solution you'd like.

I need to register a new custom endpoint in the method register_endpoints() from class Elementor\Core\Editor\Data\Globals\Controller.

Could you please add a new action hook inside this method? The variable $this must be passed as a parameter for the action hook.

This would be the updated class method:

public function register_endpoints() {
    $this->register_endpoint( new Endpoints\Colors( $this ) );
    $this->register_endpoint( new Endpoints\Typography( $this ) );

    do_action( 'elementor/controller/register_endpoints', $this )
}

The only change is that the line do_action( 'elementor/controller/register_endpoints', $this ) has been added.

Of course you could change the action name to whichever you find more appropiate.

Describe alternatives you've considered.

It can also be solved by adding a new filter in Elementor\Core\Editor\Data\Globals\Endpoints\Base by updating the method register() for the following:

protected function register() {
	parent::register();

	$args = [
		'id_arg_type_regex' => apply_filters( 'elementor/endpoints/id_arg_type_regex', '[\w]+', $this->get_name() ),
	];

	$this->register_item_route( \WP_REST_Server::READABLE, $args );
	$this->register_item_route( \WP_REST_Server::CREATABLE, $args );
	$this->register_item_route( \WP_REST_Server::DELETABLE, $args );}

Only one line of code is updated, replacing '[\w]+' with apply_filters( 'elementor/endpoints/id_arg_type_regex', '[\w]+', $this->get_name() ). The default value if no filter is added remains the same. However it allows for modifying the regex for a specific endpoint. We pass the value of $this->get_name() as a parameter to be able to check which endpoint is triggering the filter (values can currently be colors or typography).

Additional context

While the latter solution would make everything easier, the former may be easier to include without having to think about possible misuse. Both hooks could be implemented as they are compatible with each other.

Agreement

• I agree that my request may be closed without action if it doesn't meet all the requirements.