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

Support Plugins #388

Open
yassinebridi opened this issue Apr 5, 2020 · 4 comments
Open

Support Plugins #388

yassinebridi opened this issue Apr 5, 2020 · 4 comments

Comments

@yassinebridi
Copy link

I know redwood is trying to make every major operation opinionated, but supporting plugins would open a whole new world of possibilities, there definitely would be areas that redwood might not think about implementing to the core functionality, for example:

  • An image processor for optimizations.
  • Different ways of deploying, giving the ability maybe to not well-know hosting providers to implement their own solutions for redwood.

There could be an official store for the plugins that has been reviewed thoroughly, and has respected the high standards that redwood would outline.

@guledali
Copy link
Contributor

guledali commented Apr 5, 2020

I saw today that someone have already made a plugin for redwoodjs, https://github.com/freddydumont/redwood-nprogress

There has to be somewhere where you can find all plugins like centralized repo or a store similar to gatsbyjs https://www.gatsbyjs.org/plugins/

@yassinebridi
Copy link
Author

Exactly, and adding support to the redwood cli, from listing to installing/uninstalling plugins etc..

@guledali
Copy link
Contributor

guledali commented Apr 6, 2020

It would be nice if redwoodjs forced library authors to think of how people will write tests with their plugins. For example both devise and CarrierWave from the ruby community have good docs on how to write tests with them.

Redwoodjs should enforce testing culture or at very least encourage it.

@jtoar
Copy link
Contributor

jtoar commented May 5, 2022

Just wanted to add that this is something we're actively thinking about now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

3 participants