Matthias Koch
Matthias Koch
I think this should be fixed in 9.0.1... but please check and reopen if necessary.
> However, if you're trying to avoid using the serializerbuilder/deserializerbuilder you could use the emitter and manually send in the scalar's/mappings/etc. I'm not _trying_ to avoid it, it's rather that...
See https://github.com/nuke-build/nuke/discussions/1564#discussioncomment-15033327 Unsupported APIs have been removed. Note the `GetModel` methods for more advanced use cases.
This feature would never work reliably. You'd have to classify _all_ APIs as `read` or `write` operations, and encapsulate them with an aspect.
What exactly would you do if a target has `File.Delete` in it?
Then you can do the same for CLI invocations. Bottom line, like I said, the feature would not work reliably. You would not be able to walk to a build...
It isn't hidden for the most part: `ToolSettings.GetProcessArguments()` > I understand you don't want to develop this feature Not fully true. I would have liked something like this, but consistency...
I might think about adding a settable delegate in the new task implementation: https://github.com/nuke-build/nuke/blob/44173c559ea1e140840cb31bbbc91fb6c69d967e/source/Nuke.Tooling/New/ToolTasks.Run.cs#L16 But right underneath you can already see the next culprit. Attributes like `[GitVersion]` et al wouldn't...
2025.1.1 will be available in about 10 minutes. That should hopefully fix it.
@xoofx I've sent you an important email a while ago ;)