Last active
February 10, 2016 17:37
-
-
Save lemonmade/8ea2aaf0fed09301973a to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| |- app | |
| | |- assets | |
| | | |- javascripts | |
| | | | |- popover.js | |
| | | |- stylesheets | |
| | | | |- popover.scss | |
| | |- helpers | |
| | | |- ui_popover.rb | |
| | |- views | |
| | | |- styleguide | |
| | | | |- popover.html.erb | |
| |- test | |
| | |- javascripts | |
| | | |- unit | |
| | | | |- popover_test.js | |
| | |- unit | |
| | | |- helpers | |
| | | | |- ui_popover_helper.rb | |
| different repo... | |
| |- components | |
| | |- popover | |
| | | |- popover.sketch | |
| | | |- README.md |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| |- components | |
| | |- popover | |
| | | |- popover.js | |
| | | |- popover.scss | |
| | | |- popover.rb | |
| | | |- README.md | |
| | | |- test | |
| | | | |- popover-test.js | |
| | | | |- popover_test.rb |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I’ve previously worked on projects (caveat: not Rails) that made this switch. The biggest vote of confidence was from the lead dev who set up the original structure, but wasn’t deeply involved in the change. He started up a new project (we built lots of projects with the same scaffolding) and immediately fell in love with the change.
Beyond anecdotes, I sympathize with this being different from Rails conventions. OTOH, in terms of front-end, the paradigm shift has already happened. Components (not HTML/CSS/JS) are the primary way of factoring an interface. It’s not a blocker of course, but the current way is a source of conceptual friction. The assets package is a great opportunity to re-align things. I’m in favour of pursuing this at least to the next stage, where we can see in more detail what the implications are.