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
This is a "feature" of how pre- and post-actions are done and how they differ. It's subtle, so I think it definitely warrants a clear example in the documentation.
Because a pre-action is enacted before the main action, the path that's been oh-so-carefully constructed is already in position for the pre-action. Therefore, when the options of the pre-action are parsed, the current path is the expected path.
However, when a post-action is enacted then the main action has already happened, clearing the current path. Therefore it needs to restore the defined path to the current path at some point. The code that does this and that parses the options does it in the "usual" order: parse the options then set the path (this is what happens on a normal path). This means that when the spath/transform=... key is parsed then there is no current path.
The solution is the same as wanting to set an option on the main path that affects the whole path, but needing to specify it in the options before the path is constructed: to use the key spath/at end path construction.
But it works in
preaction
.The text was updated successfully, but these errors were encountered: