I have a component which used to have a lightning:icon component as

<lightning:Icon iconName="utility:search" alternativeText="search" />

it used to work until winter 18. But I was testing on Summer 18 it was failing with error.

Component class instance initialization error [Definition does not exist on the client for descriptor:markup://lightning:Icon] Failing descriptor:

<lightning:icon iconName="utility:search" alternativeText="search" />

So difference between two is only is Icon > icon. I looked into release notes to find if salesforce has removed case insensitivity of lightning component name. I event test with different lightning components they were also not working when name is used with capital letters.

Does salesforce changed this behaviour?

  • Hi @ManjotSingh. That's interesting. But what is the question? – Martin Lezer Apr 24 '18 at 12:30
  • does salesforce specified anywhere about this change? or this might be a bug they will fix – Manjot Singh Apr 24 '18 at 12:31
  • 3
    Lets wait for GA for Summer 18 before making any decisions. You can ask this on Release Readiness CHatter group. They seem to respond well there. success.salesforce.com/_ui/core/chatter/groups/… – Pranay Jaiswal Apr 24 '18 at 12:38
  • With lightning, assume case sensitivity for everything. In fact, assume it for ALL of your code and your peers will thank you. – Caspar Harmer Apr 24 '18 at 21:46

Salesforce is going to roll back case sensitivity in summer 18 org. But they are saying that salesforce is going to implement case sensitivity in upcoming releases. Lightning:components were supposed to be case sensitive. They shared a link of summer 15 release notes. So you can check that all your components are case sensitive before upcoming releases.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.