Deployment Package and missing diffs in Illuminated Cloud
akippiko
I am using Illuminated Cloud for Salesforce and would like to ask about
the behavior of Deployment Packages and diff detection.
My SFDX project is configured as follows:
- In sfdx-project.json, only one packageDirectories entry is defined.
Its path is `force-app/main/package-a`.
- A namespace is configured for the project.
- In Illuminated Cloud, the Module settings show the Deployment Package as `<default>`.
In this setup, there are clear metadata differences between my local project
and the connected org (sandbox or scratch org).
However, Illuminated Cloud does not detect any differences
when running compare or retrieve operations.
From the behavior, it appears that Illuminated Cloud may be referencing
`force-app/main/default` instead of the actual package directory
`force-app/main/package-a`, and as a result the correct metadata
is not being compared.
My questions are:
1. What path does the `<default>` Deployment Package actually refer to?
2. When only a single packageDirectories entry is defined,
is `<default>` always expected to point to that path?
3. Is there a way to explicitly configure `force-app/main/package-a`
as the Deployment Package in Illuminated Cloud?
4. Are there any cache, index, or configuration items that should be checked
when diffs are not detected correctly?
For reference, I have already run “Rebuild Caches and Indices”.
Thank you for your help.
Scott
Hi. The deployment package is not likely relevant for your use case. That is specifically for ensuring that deployment associates deployed metadata with a package for first-generation packaging. The value <default> is what you’ll see unless you’re actually workng on 1GP.
The default package directory designated in sfdx-project.json is the one that should be used when retrieving metadata that is new to the local project to ensure it’s placed in the desired/correct location. Since you only have one package directory in that file, it should be the default package directory. IC also has its own notion of a default source root in Illuminated Cloud | Configure Module, but it’s only relevant if the project has multiple configured source roots. You can certainly see if it’s set to something other than force-app/main/package-a, though.
If you’d like, you can enable debug logging for Metadata Retrieval and Salesforce DX, reproduce the unexpected behavior, and share the resulting idea.log with me via email for review. I’d also need you to explain the expected result vs. the actual result so I can use that information to understand what I’m seeing in the log.
Regards,
Scott Wells
akippiko
The issue is resolved now — it was caused by multiple source roots being
configured. After setting a single source root and rebuilding caches,
everything works as expected.