Replies: 1 comment
-
|
You should only have to define them once under the [move] section of your configuration. It was a mistake in the docs that the path config options were below the "import" plugin instead of the "move" plugin, which I've gone ahead and opened a PR for #331. If you're still having issues where the paths defined under the [move] section aren't being respected, please open up an issue with some more details as it would be a bug at that point. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm finding that I have to define my paths in both the [import] section and the [move] section for both actions to result in the same path result. For my usecase (and I have to imagine most usecases), they should always be the same. If you're just using the default path, no big deal, but I'll be doing a bunch of deviations from that, with plugins handling some of the modifications, so it could get quite involved. Any way to config so only defining them once is necessary, instead of having to be sure any changes are replicated to both sections?
Beta Was this translation helpful? Give feedback.
All reactions