Cool! After a hiatus from Rails, I threw together an internal tool this week with 6.0.0.rc2 - breath of fresh air in a world of microservices and complex architectures.
Good job rails team!
===
Edit:
P.S. - Thanks rails community too! Was super simple to build thanks to the vibrant community...
- Corporate SSO via devise + omniauth
- CSV uploads (activerecord-import gem)
- pagination (will_paginate gem)
- external API integration
- DB seeding
- audit logging on edited/created data (audited gem)
Conventions in rails are so strong, that I quite possibly know how to seed and migrate your database, can integrate additional omniauth providers and know how to pull audit data even without looking at your code.
on a whim...do you know of any good guides for integrating an external API? i'm new to rails and working on a rails project that needs to communicate with a third party api -- there are a lot of messy guides, particularly for oauth
If I was starting out fresh, I'd probably try and check out some of the guides that services like stripe and github have for interacting with their own api's if you'd like some real world experience.
I think the pattern of making generic classes that leverage the httparty gem is solid. Depending on your preference have another layer of classes between that and your models. Or have the apis called directly from models or controllers
I don't know of a library for external API integration (so I'll be watching this space), but for OAuth specifically, Omniauth has been invaluable. It supports a lot of various strategies [0] which is what it called various OAuth2 implementations.
Good job rails team!
===
Edit: P.S. - Thanks rails community too! Was super simple to build thanks to the vibrant community...
- Corporate SSO via devise + omniauth
- CSV uploads (activerecord-import gem)
- pagination (will_paginate gem)
- external API integration
- DB seeding
- audit logging on edited/created data (audited gem)
- wizards (wicked gem)
- etc, etc.