Handle error when controller not found

[tmaier]

Lets assume I am referencing a controller at data-controller="does-not-exist", which does not exist.
This can happen due to a typo - or because the controller has not been loaded for some reason (e.g. not in the load path, caching issue etc.)

When I see it correctly, this would never get raised. Not as an exception. Not even when the debug mode is enabled.

What is the rigtht approach to get this noticable? I would prefer if I can see it in my console when debug mode is enabled and when this will be handled by Application#handleError.

[tmaier]

I believe this is the culprit:

stimulus/src/core/application.ts

Lines 80 to 83 in 7b810ec

	getControllerForElementAndIdentifier(element: Element, identifier: string): Controller | null {
	const context = this.router.getContextForElementAndIdentifier(element, identifier)
	return context ? context.controller : null
	}

It just swallows (returns null), if no controller has been found

[Ted-Tash]

@tmaier

Hello, if it is OK with you, I would love to work on this. My coworkers and I were speaking of this exact issue, and I thought it would be a fun way to contribute. I was excited to see someone had already opened an issue to track it.

[tmaier]

Hi @Ted-Tash, this would be great!