-
Notifications
You must be signed in to change notification settings - Fork 38
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
ValueError: Pipline step in unexpected format: {'pyspelling.filters.html': None, 'comments': False, 'ignores': ['code', 'pre']} #60
Comments
@Sid-ah This is really an upstream PySpelling question. I imagine your issue is that you need to indent The short of it is that YAML can be finicky about indentation in these cases. Options keys need to be nested under the filter name key, not at the same level as the filter name. It thinks you have a multi-key dictionary for your HTML filter. Not a dictionary of options nested dictionary under it specifying option names. This is not what you want: namekey:
optionkey: bad This is what you want: namekey:
optionkey: good Users will think they are disabling comments in your example, but they are not actually, so we identify this scenario and throw an error so the user is aware. Try this which nests the options as a separate dictionary under the filter key. matrix:
- name: Markdown
aspell:
lang: en
dictionary:
wordlists:
- .wordlist.txt
encoding: utf-8
pipeline:
- pyspelling.filters.markdown:
- pyspelling.filters.html:
comments: false
ignores:
- code
- pre
sources:
- '**/*.md'
default_encoding: utf-8 |
Thank you @facelessuser! Fixing the indentation did the trick for me. |
No problem, glad I could help 🙂 . |
Thanks @Sid-ah and @facelessuser I have updated the documentation describing the remedy to avoid this issue, based on your input to this issue. |
I tried to follow the example below, but I'm getting some errors.
Here is the error I'm getting:
I was able to resolve it by removing the pipeline step. Is this a known issue? This is a recent issue as I have used this action for some time now.
The text was updated successfully, but these errors were encountered: