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

v3 Feedback #2815

Open
harlan-zw opened this issue Oct 17, 2024 · 0 comments
Open

v3 Feedback #2815

harlan-zw opened this issue Oct 17, 2024 · 0 comments

Comments

@harlan-zw
Copy link
Contributor

harlan-zw commented Oct 17, 2024

Hi there, I saw the v3 was recently published so I thought I'd have a play around.

Instead of spamming several issues, I thought I'd make this one to track. I'm not sure if it's in a state where you're welcoming issues / PRs so let me know how I can help.

  • Config is currently only resolving through root path, we should ideally support the srcDir (/app in nuxt v4). Ideally logic should be similar to @nuxtjs/mdc see (https://github.com/nuxt-modules/mdc/blob/main/src/module.ts#L106)
  • It does not seem possible to load in the content dir with your own prefix as the default collection overrides it
  • Using a collection name with a - in it throws an error, this is due to a SQL error (ERROR Cannot start nuxt: near "-": syntax error)
  • SQL errors aren't exposed properly as above, the SQL should be returned so the user can debug on their end.
  • Using the source as an object is a bit confusing, I think it would be clearer if paths was include and was defaulted to **/*.md for page types
  • For Nuxt SEO I am pulling content from each individual github repo, it's not possible for me to set these up under one collection which makes querying nav quite difficult. It seems like a collection should support multiple sources or we should be able to query all collections easily.
  • Inline code such as `<div>hello world</div>` is being converted to ProseCode instead of ProseInlineCode. This seems to be known given the component override.
  • queryCollectionNavigation appears to be generating nested items when they shouldn't be only sometimes

Image

I'll add more items as I continue with the integration however please feel free to close once reviewed.

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