Timeline for Plans for obfuscation of Lightning Component source when delivered in a managed package?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 22, 2018 at 2:39 | comment | added | Diego | @dzh Basically we will deliver code minification and potentially some obfuscation prior. But at the end of the day is JS code, anyone bored enough can reverse engineer the code, as of for any web property in the world. | |
| Feb 21, 2018 at 1:31 | comment | added | dzh | I have a hard time believing there is a reliable way to achieve this, by definition. I would love to see the details of this before false sense of security is released to the wild. | |
| Nov 14, 2017 at 1:35 | comment | added | Diego | Sorry for the delayed answer, I spoke to the PM. It is on the roadmap, but not sure when will be GA. Probably within the next couple of releases. | |
| Sep 11, 2017 at 19:28 | comment | added | Eric | @Diego - Do you have any update with this? Currently all code within a managed package as it relates to Lightning is visible to clients | |
| Aug 18, 2017 at 7:13 | comment | added | Keith C | Thanks Diego, will be re-assuring to know what the plan is. | |
| Aug 18, 2017 at 5:26 | history | answered | Diego | CC BY-SA 3.0 |