Closed darekkay closed 3 years ago
hello @darekkay , can I work for the Random Image as stand alone widget?
Sure @adrianrios25 🚀
@adrianrios25 hey I was about to work on the same/similar widget. If you need any help tell me how to get in contact and we could work on it together.
hi @darekkay I created a youtube stats widget
what do you think? if I send a pull request, should I include both server and client side in one request? or should I separate it?
Thanks @adrianrios25 , it looks good 🚀 One PR for both client & server is fine
@darekkay , I created a PR for the youtube stats.
Hello @darekkay , I found this inspirational quote api while browsing some repos, I think this can be a good widget, we can create a random inspirational quote. https://github.com/vinitshahdeo/inspirational-quotes
what do you think?
@adrianrios25 I've also found this quotes project a few weeks ago and was thinking the same, so sure! 🚀
Hey @darekkay
I have two great ideas aboutthis.
This is to support the small cases, where most people need to do perform GET request. THus will cover lot of scenarios!
Basically people use webhook to get the latest blog post, build status etc. So thinking of generalised panel for this, given it should be cachable. If it's okay for you , iwould try to add. But i am not expert on front-end side (espcially react)
Hey @peeyushsrj , thank you for your ideas!
Simple Integration of API ( So each widget would request to url provided at the creation time of widget)
Currently, there are two file generators:
Run yarn generate
(or npm run generate
) in the app
module to create a widget boilerplate. Select yes
at the Does your widget use sagas (e.g. fetch external data)?
prompt, and a sagas.js
file will be created with some data-fetching code.
Run yarn generate
in the server
module to create a server route.
There's probably some more room to improve the boilerplate code, but for me it has been good enough. I'm open to improvements, though 🙂
Integration of webhook
I've created #25
I've enabled Discussions in this repository, so this placeholder issue is no longer needed.
There are many widget ideas for the Dashboard. This task is a placeholder for people to find a new widget they would like to work on.