Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

call-tokenuri should error if no explicit outputFilename is defined #340

Open
TimDaub opened this issue Oct 24, 2022 · 0 comments
Open

call-tokenuri should error if no explicit outputFilename is defined #340

TimDaub opened this issue Oct 24, 2022 · 0 comments

Comments

@TimDaub
Copy link
Collaborator

TimDaub commented Oct 24, 2022

  • It's very unlikely that we'll ever use call-tokenuri without a specific outputFilename
  • hence it should error when outputFilename isn't defined in a crawlpath
  • now we're currently not aware of outputFilename within a strategy and that's part of the problem to solve in this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant