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
fix: ContentQuery _path
not used properly (#1141)
#1143
Conversation
β Deploy Preview for nuxt-content ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Hello @GerryWilko π I added a small comment to your PR, I was already working on the fix! If we can merge this branch, I can continue my work on tests for these components on mine. π Waiting for your feedback! |
_path
not used properly (#1141)
Hi @Tahul yep that makes sense to me! I thought it was a bit odd that the path sanitizing was in multiple places so pushing into the existing content query makes sense to me. I was trying to accept your change but it looked like it was going accept it in a strange place unless I misunderstood the preview GitHub was showing me. I haven't used the suggested change feature myself so not very familiar with it π Thanks for the approve! |
_path
not used properly (#1141)_path
not used properly (#1141)
π Linked issue
#1141
β Type of change
π Description
Content queries didn't seem to be working quite right when querying folders. If there was a matching exact file then it seemed to work ok but
ContentList
andContentQuery
that were pointing at folders seemed to be broken.Looks like the intention was for the path was to match the start allowing a list of all child content pages to be returned.
π Checklist