If the LookAndFeel folder doesn't exist when validating the FlatLaf module, then register the nbfs URL for the folder instead.
When I first added this in #4719 I'd considered a possibility was also for modules to be able to register these files in the layer system, particularly in a platform application. But I didn't test for this use at the time. It turns out this doesn't work, because the layer files aren't mounted during module validation.
We might just use the URL full stop, but I've left the previous logic as is for now. I'm not 100% sure if the local / system config files can result in different URLs?
I think this is a quick, safe fix for delivery, but feel free to ask to retarget.
If the
LookAndFeelfolder doesn't exist when validating the FlatLaf module, then register thenbfsURL for the folder instead.When I first added this in #4719 I'd considered a possibility was also for modules to be able to register these files in the layer system, particularly in a platform application. But I didn't test for this use at the time. It turns out this doesn't work, because the layer files aren't mounted during module validation.
We might just use the URL full stop, but I've left the previous logic as is for now. I'm not 100% sure if the local / system config files can result in different URLs?
I think this is a quick, safe fix for delivery, but feel free to ask to retarget.