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

Bug in components with properties at the beginning of a line #12

Open
6 of 7 tasks
ldonetti opened this issue Sep 9, 2024 · 0 comments
Open
6 of 7 tasks

Bug in components with properties at the beginning of a line #12

ldonetti opened this issue Sep 9, 2024 · 0 comments

Comments

@ldonetti
Copy link

ldonetti commented Sep 9, 2024

Describe the bug

I'm using Sli.dev and I observe a regression when markdown-it-mdc is upgraded from version 0.2.3 to 0.2.4 (see this issue). I started to get Internal server error: Invalid block params when using the MDC syntax for vue component with parameters.

For inline component I found out that the error is only triggered when the component is the first element on a line. For example:

 Inline :component{key="value" key2=value2}!

works, but not

:component{key="value" key2=value2}!

Similarly, block components with parameters also give an error.

Reproduction

PR #13

System Info

System:
    OS: Linux 6.8 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)
    CPU: (8) x64 Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz
    Memory: 10.07 GB / 15.29 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 18.19.1 - /usr/bin/node
    npm: 9.2.0 - /usr/bin/npm
  Browsers:
    Chrome: 128.0.6613.119

Used Package Manager

npm

Validations

  • Follow our Code of Conduct
  • Read the Contributing Guide.
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
  • The provided reproduction is a minimal reproducible of the bug.

Contributions

  • I am willing to submit a PR to fix this issue
  • I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
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