Don't think there's an efficient way of doing this. You'd pretty much have to run the import steps recursively until there were no imports left to do and then compare the resulting text for changes.

It will however be a common painpoint for anyone trying to organize their code.

Comments

allain’s picture

allain commented

Since it's only a problem during active development, Hugo has suggested adding an "Always generate" configuration setting.

rhache’s picture

rhache commented

+1 for an "always generate" setting

allain’s picture

allain commented

Does the reliance on Drupal's CSS Caching functionality make this a non-issue?

We now deal with this the same way Drupal's caching handles @Import processing.

More investigation is required...

rhache’s picture

rhache commented

Hi Allain,

Reliance on Drupal's caching indeed solves the issue. Love how this works.

Sincerely,
Rene

allain’s picture

allain commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.