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.

Sign up for GitHub

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

Jump to bottom

Rename plugin semantics #100

Open
tonyketcham opened this issue Aug 8, 2022 · 0 comments · May be fixed by #105
Open

Rename plugin semantics #100

tonyketcham opened this issue Aug 8, 2022 · 0 comments · May be fixed by #105
Labels
resolvers Adding functionality on top of the GraphQL schema sources Interacting with data sources transformers Converting source data to GraphQL data

Comments

@tonyketcham
Copy link
Collaborator

We should follow a standard pattern for naming of the plugins and their exports. These exports should also be named rather than exported as default so that a standard name is used in our documentation and ecosystem consumption of the plugin

  • markdownTransformer exports transformMarkdown()
  • resolverSvimg exports resolveSvimg()
  • providerApollo exports provideApollo()
  • sourceFilesystem exports sourceFilesystem()
@tonyketcham tonyketcham added transformers Converting source data to GraphQL data sources Interacting with data sources resolvers Adding functionality on top of the GraphQL schema labels Aug 8, 2022
@tonyketcham tonyketcham linked a pull request Aug 12, 2022 that will close this issue
Open
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
resolvers Adding functionality on top of the GraphQL schema sources Interacting with data sources transformers Converting source data to GraphQL data
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Rename exports & cleanup FlatbreadLabs/flatbread
1 participant
@tonyketcham