You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
thescientist13 opened this issue
Apr 24, 2021
· 0 comments
· Fixed by #669
Assignees
Labels
CLIdocumentationGreenwood specific docsPluginsGreenwood PluginsquestionFurther information is requestedRFCProposal and changes to workflows, architecture, APIs, etcv0.15.0
There have been a couple discussions and opportunities observed coming out of #508 / #509 and while working on a private project idea of my own
plugin-graphql added the support to merge custom schemas provided by users in a data/schema/ directory in the user's work space. Could plugins get that support as well, so plugins can ship custom queries and schemas? This could could allow for entire plugins of functionality like adding a photo gallery that could handle mapping paths to resolvers
a private project of mine, where sharing templates and pages would allow plugins to provide entire "theme" packs with templates and styles ready to go out of the box
Details
Off the top of my head, I wonder if this is something that could just be done by using ResourceInterface and hijacking any files that you own? Or would you have to open up "context" to support providing additional directories for Greenwood to look at.
For example, to "share" a custom page template for use in a markdown file from a plugin
---template: 'acme-themepack-splashpage'---## Welcome to my site!
Lorum Ipsum
The page template would be able to resolve to something like node_modules/acme-themepack/src/templates/acme-themepack.html
Not sure if ResourceInterface is enough?
classMyThemePackResourceextendsResourceInterface{constructor(compilation,options){super(compilation,options);this.extensions=['.html'];this.contentType='text/html';}// if request matches a file we "own", resolve it// ex: `${userWorkspace}/templates/themepackXYZ-splash-page.html`asyncshouldResolve(url){returnPromise.resolve(true);}}
Or if Greenwood needs to open up a new API, so creating this issue to track that cases are developed for, and to report back what the developer ergonomics are like and see if something new needs to be made.
For bonus points, we could also look to incorporate #574 ? 💡
The text was updated successfully, but these errors were encountered:
CLIdocumentationGreenwood specific docsPluginsGreenwood PluginsquestionFurther information is requestedRFCProposal and changes to workflows, architecture, APIs, etcv0.15.0
Type of Change
Summary
There have been a couple discussions and opportunities observed coming out of #508 / #509 and while working on a private project idea of my own
Details
Off the top of my head, I wonder if this is something that could just be done by using
ResourceInterface
and hijacking any files that you own? Or would you have to open up "context" to support providing additional directories for Greenwood to look at.For example, to "share" a custom page template for use in a markdown file from a plugin
The page template would be able to resolve to something like node_modules/acme-themepack/src/templates/acme-themepack.html
Not sure if
ResourceInterface
is enough?Or if Greenwood needs to open up a new API, so creating this issue to track that cases are developed for, and to report back what the developer ergonomics are like and see if something new needs to be made.
For bonus points, we could also look to incorporate #574 ? 💡
The text was updated successfully, but these errors were encountered: