Closed Oleafeon closed 1 year ago
Thanks!
I'll have to look into how to get the plugin noticed without the configuration file mapping the plugin/file extension. Hopefully won't be too long 🙂
allright thank you
@JohnathonKoster Did you have a change to get this working?
I have not yet - will make a note to dig into it this week
Do you have an example of the GitHub action you are running? Thanks!
@JohnathonKoster yes here you go
name: Code style checks
on: pull_request: branches:
jobs: code-style-checks: name: Code style checks runs-on: ubuntu-latest
steps:
- name: Checkout the branch
uses: actions/checkout@v3
with:
ref: ${{ github.head_ref }}
- name: Checking HTML code
uses: creyD/prettier_action@v4.3
with:
prettier_options: --check ./resources
Thanks for the sample. After debugging and experimenting, this is the same issue as described here:
https://github.com/creyD/prettier_action/issues/110
Removing the plugins array from the .prettierrc.json
file works, but is likely not ideal for setups in editors. Was able to replicate this using both the prettier-plugin-antlers
and prettier-plugin-tailwindcss
plugins independently.
Describe the bug When implementing this plugin i came to the problem that the my github actions fails this is the log that i get
Impacted Products Which Antlers Toolbox products does this bug apply to?
Versions and Other Plugins/Extensions