Unable to Create/Save Lightning Design Component
When trying to create a <design:component> in an aura bundle I receive the following error:
2018-04-04 13:46:49,248 [703408567] DEBUG - .ForceComBuildFailureAnnotator - Adding external annotation: Problem type = ERROR Problem message = FIELD_INTEGRITY_EXCEPTION - null: Source Line number = 0 Column number = 0
This bug is blocking me from being able to work inside of the Illuminated Cloud 2 plug-in and having to rely instead on the Developer Console to do development work. This is a major inconvenience and while it is not completely a blocker it does cause a shift in scope on time since I either would need to work fully inside the Developer Console or switch back and forth to get the work sussed out.
Reproduction Steps:
- Create Aurabundle
- Generate test component and possibly test controller
- Right click on the folder for the bundle
- Click 'New'
- Click 'Lightning Design'
- Error should happen right away/otherwise try and save.
- Error is generated
Comments (7)
-
repo owner -
repo owner The issue did not reproduce for me. Let's gather some additional diagnostic information if you don't mind. First, let's reproduce the issue with debug logging enabled for metadata deployment as documented here:
http://www.illuminatedcloud.com/support/debuglogging
Once you reproduce it, please provide the full log of the reproduction.
Then let's see if this is a Tooling API vs. Metadata API thing. Under Illuminated Cloud>Configure Application>Validation and Deployment, please disable Prefer Tooling API for>Lightning and try again. If it succeeds, that makes it clear that the issue is with the Tooling API deployment path.
Between the two of those, hopefully I'll get enough info to understand why this is failing for you and how to address it. Thanks!
-
reporter Looked more into it and identified the issue. It is not in your software but in the design of the error coming from Salesforce. I was able to reproduce it within the Dev Console as well. It was in relation to the <design:attribute> and the requirement of the 1:1 match in a component. There was an issue on naming that caused the issue.
It was more Salesforce not having a well defined error versus the developer.
Thank you for the quick response though.
-
repo owner Ah, nice! Thanks for digging in and finding the issue. I always hate when I can't reproduce a problem that a user is seeing...
-
reporter Yeah unfortunately your program would be gigabytes large if you tried to catch every possible Salesforce error and translate it into a readable error for the developer.
Thanks again. I am going to close this so it is off your list!
-
reporter - changed status to resolved
Development issue w/ error being thrown from Salesforce and unrelated to Illuminated Cloud 2.
-
repo owner - changed component to Metadata Deployment/Retrieval/Removal
- Log in to comment
Let me take a look and see if I can reproduce the issue. More to come shortly.