-
-
Notifications
You must be signed in to change notification settings - Fork 967
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
Create the riot components organization #427
Comments
Go ahead! I'm happy to support it :) Makes perfect sense to have one, but my time will go to maintaining this repository. |
I think we should agree on the specs otherwise we need to update all the components anytime there will be an riot API change. In any case I'd keep working on the riot tests and code coverage and once we're done I will start working on the components repo |
So glad you find that interesting! The specs will obviously tighten in time but any particular specs you are referring to? Leaving/taking out custom tags on the resulted HTML layout? API specs? |
👍 |
Looks clean. And this spec would be part of the component repository, right? |
Any further progress on this? I have a few components I'd like to share with the world. 😄 |
I am building crud-forms component for RiotJS, my current stack works like this: In a sense I would have fully declarative method for generating CRUD applications without writing any extra code. I will be done with this some time next week. EDIT: My solution would work very well with other components that generate views from JSON collections and forms by JSON Schema + other metadata, and some parsers which can transform REST API back-ends self documenting features to usable format by the forms. |
Awesome! |
Unfortunately the company I am working for decided to go switch for React, since the RiotJS each-feature seems to be broken / behaves in unexpected ways (the data set provided for the each-feature does not match what gets parsed after updates). I personally prefer the Riot development philosophy over React, so I might be contributing outside of work instead. We will build something ready and working with React and then I will recycle the best ideas to Riot world. The basic premise seems to be working (easy to configure CRUD UI which talks with any REST API without additional code) and this will change the way I can use any Cloud services when prototyping new features. If you are up for the 12 startups in a year challenge, this will be the tool of choice. |
Hoping to stabilize Riot soon and make it more performant. Thank you for the nudge! |
I've created an organisation for Riot Components that you might be interested in. I've called it RiotGear. I plan to build more components and keep it updated and hopefully turn it into a popular goto place for custom Riot tags. I'm in the middle of building components and building the website. The components need tests and the website needs a refactor, but it's taking shape. Repos: https://github.com/RiotGear If you'd like to suggest new components or enhancements to existing ones please raise an issue here: https://github.com/RiotGear/riotgear.github.io/issues I'd like to hear any thoughts on the above from the Riot core devs, happy with my plans? Any ideas you'd like me to consider? Keep up the good work with Riot, I'm an Angular convert, I love it! |
@gregorypratt RiotGear looks an awesome project send us a pull request adding a link to it in our readme file once you are done |
Nice! I'm sure that will be useful once you get all those components finished. Looks like you have some decent amount of work ahead :) |
Thanks for the positive feedback! It's definitely a decent amount of work but Riot makes it quicker than I expected. So far I have:
On the to do list:
Plus the install/example/about documentation. If anyone has any requests raise an issue: https://github.com/RiotGear/riotgear.github.io/issues Otherwise once it's finished I'll fire over a PR... ;-) |
Nice to hear. Looking forward to that. |
RiotGear link added to components section #427
You made it public! Very cool. Almost closed this issue, haha. |
closing this issue due to inactivity |
What about creating a github organization to host all the riotjs components? Something similar to http://customelements.io/
The text was updated successfully, but these errors were encountered: