-
Notifications
You must be signed in to change notification settings - Fork 13
Code FAQ
Arnol Fontalvo edited this page Jan 30, 2018
·
20 revisions
- What is the overall architecture of the platform?
- What is the purpose of react-on-rails?
- How do we use Action Cable?
- How do we use resque and background jobs in general?
- What work is Roar doing?
- The app's data model is heavily dependent on Action Network's API. Any gotchas there?
- Does the architecture provide any systematic way to distinguish what data is and is not synced to ActionNetwork? (Eg: a module that is always included in models that are synced, and never mixed in to ones that should not? Or a decorator that always wraps synced classes? Etc...)
- Why minitest/fixtures instead of rspec/factorybot?
- What is the testing strategy for frontend code?
Database ERD erd.pdf
Rails has an assets pipeline, it was simple and handled basic things.
When people started using webpack and other code bundling tools, it was an issue working on Rails applications that handle front-end logic with tools like react, vue or angular because of the way those projects defined dependencies.
Now, you are able to have the rails assets pipeline "understand" those dependencies and build appropriately the js that is served in the web application.
It takes some time to get used to, but newer versions of rails comes with this in place by default. So it should get easier, and easier with time to get used to it. - Arnol