Kevin Bond

Is this in response to the slack issue by @maartendekeizer?

Hi @igordeveloper, sorry for the delay - I've been on vacation. Yes, you'll need to add an alias as it's trying to match the route on the class name.

> Is there any other way to fix this, besides inserting autoconfigure: false for this service I don't think so. Some work needs to be done with how checks are...

Right now, you'll need to add `autoconfigure: false` to your config to avoid 2 instances being registered: ```yaml monitor.check.custom: class: App\Diagnostics\Check\CustomCheck autoconfigure: false arguments: - [ xhprof, apc, memcache ]...

I'm not immediately seeing a great path to a solution. The following is true: 1. It's valid for a check to have multiple `liip_monitor.check` tags (to add to multiple groups)....

I guess the script could detect or be configured in composer.json?

> I don't think trying to auto-detect the build tool would work - for example I run Yarn but inside a Docker container. We could detect `yarn.lock` vs `package-lock.json` to...

I'm going to ping @weaverryan about this as I'm a bit out of my element here. Where are you thinking this should live? encore-bundle?

> How would this work with exposed properties? Like, if “title” is exposed, i guess the security check would still be applied only to the top-level post, right? Yes, that...

I discovered this currently can't work as twig snake-cases variadic properties. For `{{ component('my_component', prop1: 1, prop2: 2) }}`, `prop1` and `prop2` are received as `prop_1` and `prop_2`.