LWC allow access to "key" attribute for controller event handlers Platform / Developer Tools Key is a required attribute when using iterators like for:each within a LWC. // TODO [#3100]: Update message to point to external documentation once available. Is there a reason why it would be a bad idea to make a new delegate: That way the sender will be typesafe and I can pass whatever the heck I want as the arguments (including custom EventArgs if I so desire). Even experienced people might. ', 'Invalid lwc:ref usage on element "{0}". Find centralized, trusted content and collaborate around the technologies you use most. Internet Explorer doesnt support the CustomEvent interface natively, but the Lightning Web Components model adds support for it. Open it and see your component working in the UI. Not the answer you're looking for? The number of distinct words in a sentence, Can I use this tire + rim combination : CONTINENTAL GRAND PRIX 5000 (28mm) + GT540 (24mm). This application is a product selector for a bicycle shop. So in certain circumstances there are valid security concerns as to why you should use the standard pattern. Connect and share knowledge within a single location that is structured and easy to search. The following example illustrates this technique. ', "Template expression doesn't allow computed property access", '{0} directive is expected to be an expression', 'Invalid id value "{0}". For more information, ', 'please visit https://sfdc.co/template-directives', 'lwc:preserve-comments must be a boolean attribute. s in template () * feat: add handling of lwc:data-bind directive * feat: add handling for lwc:slot-data directive * feat: add capability in engine to accept a factory function as slot content ", '{0} is not valid attribute for {1}. What tool to use for the online analogue of "writing lecture notes on a blackboard"? To learn more, see our tips on writing great answers. And its just an user interface for internal users (LEX, I guess), Thank you for your feedback. The key attribute should be applied to an element with for:each or iterator:*, or to a direct child of a