Posted both here and on Slack as we migrate from the latter to the former.
What is the best way to ensure that a CSS file bundled in a plugin is included in the resolve scope of a project CSS file?
I’ve tried implementing both indexedRootsProvider and resolveScopeEnlarger just as I have in the past for this same need in JavaScript, but my implementations of those EPs are not being called.
Digging in with the debugger, resolution is happening in CssCustomPropertyReference#multiResolve() which calls CssUtil#getCompletionAndResolvingScopeForElement() which in turn calls CssUtil#getCompletionAndResolvingScopeForModule() which does not consult those standard EPs for extending the resolution scope.
It does, however, call ScriptingLibraryMappings#getLibraryScopeForFile(), so it looks like I could implement that EP to make this work, but it just doesn’t seem right to implement a JavaScript plugin EP to extend the resolution scope for a CSS plugin element/file.
Anyone have any insights into the best way to make sure that bundled CSS files are included during resolution from project CSS files?
UPDATE: I’ve worked around this by adding completion and reference contributors for CssCustomProperty elements that use the bundled files. This, of course, still required registration of the custom indexedRootsProvider so that the referenced files are properly indexed, but I have it working. I can’t imagine that this is the correct/desired behavior, though. Shouldn’t indexedRootsProvider and resolveScopeEnlarger be used for resolution by the IDE’s own plugins?