You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First, I have read all the issues about config files in resource jars etc. In my understanding, the problem with these approaches is that FormatterSteps are immutable states that must be compared to determine whether something has changed. For this comparison, the config files' content must be read at configuration time. This prohibits lazily extracting these files from the resource jar to the build directory because they have to exist before the build even starts.
However, wouldn't it be possible to use something like @InputFile RegularFilePropery as an alternative? It would leverage gradles mechanism of up-to-date checking and allows developers to wire outputs from other tasks as inputs to spotless.
The text was updated successfully, but these errors were encountered:
First, I have read all the issues about config files in resource jars etc. In my understanding, the problem with these approaches is that
FormatterStep
s are immutable states that must be compared to determine whether something has changed. For this comparison, the config files' content must be read at configuration time. This prohibits lazily extracting these files from the resource jar to the build directory because they have to exist before the build even starts.However, wouldn't it be possible to use something like
@InputFile RegularFilePropery
as an alternative? It would leverage gradles mechanism of up-to-date checking and allows developers to wire outputs from other tasks as inputs to spotless.The text was updated successfully, but these errors were encountered: