demo cleanup into single directory #624
Comments
Can I recommend not folding everything into a single folder. It may be easier to maintain, but it shows a pattern that we don't want people to use. I've noticed that when we write a sample of any kind, users pretty much copy and paste what they see. Besides, knowing how to structure an AngularDart app into the correct directories is a useful thing that we can pass along to our users. Let's use the web/, lib/, test/ structure recommended for Dart apps? |
@shailen can you tell me more about your concern? Having multiple demo folders on which we quick test angularDart is real pain point for us. I don't see how anyone could assume that they should put multiple apps into a single folder. |
Would changing the folder name from demo to test_app help clear up the confusion? |
I would recommend changing demo/ to example/. This is the official Pub recommendation. And then making each app its own folder inside example/. So example/todo, etc. And then within each example, I would configure the code carefully so that reusable code goes under lib/, web code goes under web/ and test code under test/. Also, Pub does the right thing for packages/ in subdirectories of example/, so if you wanted, you could have a common pubspec.yaml for all the apps. Honestly, you'd be surprised how much people cut and paste. Its always better to followed best practices. |
I don't know if this is related, but now some of the links to angular_dart samples (dartlang.org) are broken. See https://www.dartlang.org/samples/#angular_dart |
They work for me. What kind of error do you see ? what browser ? |
Sorry, not the demos themselves, the link to the sources. E.g., ToDo source yields a 404. |
Currently the demo folder his different directories for each demo. This makes it hard to maintain. Need a single directory for all demos, each demo different name. This way single pub serve can serve them all.
The text was updated successfully, but these errors were encountered: