-
-
Notifications
You must be signed in to change notification settings - Fork 263
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
feat(content): add support for accessing content files within nested folders #286
feat(content): add support for accessing content files within nested folders #286
Conversation
Updates injectContent to allow a custom prefix to be used for content subdirectories
Updates injectContent to allow a custom prefix to be used for content subdirectories
…nto 282-content-files-with-prefix # Conflicts: # packages/content/src/lib/content.spec.ts # packages/content/src/lib/content.ts
Updates Content Routes doc to show how Analog supports content subdirectories
✅ Deploy Preview for analog-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for analog-app ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for analog-blog ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Updates subdirectory example file tree
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Awesome! @allcontributors add @BaronVonPerko for code,doc |
I've put up a pull request to add @BaronVonPerko! 🎉 |
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
Which package are you modifying?
What is the current behavior?
The current
injectContent()
does not support subdirectories within the content folder.Issue Number: #282
What is the new behavior?
This allows the existing string parameter for the routeParam to remain the same, but also allows the developer to pass in an object instead, consisting of the routeParam key as well as the subdirectory name.
Does this PR introduce a breaking change?
Other information