search

ga-wdi-boston / ember

Introduction to Ember.js
Other
9 stars 112 forks source link

use tree -L 1 #22

Open payne-chris-r opened 7 years ago

payne-chris-r commented 7 years ago

Using tree gives you a massive tree that isn't very helpful. Setting the flag tree -L 1 gives you the one you want. cc @raq929

raq929 commented 7 years ago

Really, the issue is that it shows all the npm modules and bower components. So if there's a way for it to show 2 or 3 deep without showing those, I would be very happy.

MicFin commented 7 years ago

Seems like tree -L 1 has too little information but tree -L 2 includes all the node modules so it is too much. I personally think the diagram we have in the talk is sufficient without tree at all.

$ tree -L 1
.
├── CONTRIBUTING.md
├── Gruntfile.js
├── LICENSE
├── README.md
├── STYLE.md
├── app
├── bower.json
├── bower_components
├── config
├── ember-cli-build.js
├── grunt
├── node_modules
├── package.json
├── public
├── testem.js
├── tests
├── tmp
payne-chris-r commented 7 years ago

I'm fine with removing the tree section altogether. I think #34 might address this too.

jrhorn424 commented 7 years ago

My preferred approach for showing structure is to use tree to generate a nice chunk of text, edit it manually, and paste it in a fenced code block in the README. I think I'm ok with getting rid of tree here.