Paths should follow the styleguide
See original GitHub issueFollowing the Houston app demo;
- The directory structure need to be only including routes (not components, services or pipes). Components, services and pipes need to be in an
_
directory inside the route The following commands need to be changes (feel free to check those that are solved):-
new
: simply a matter of updating the scaffold. -
generate
:-
component
/service
/pipe
: need to be added to an_
directory in the route specified. For example,ng generate component foo/bar/blah
should be generated in the directoryfoo/bar/_/blah
. If the_
is included then we don’t need to add it (an_
route would be invalid here). -
route
: the scaffold need to include an empty_
directory under the route itself.
-
-
- Adding an
index.ts
file to all scaffolds that export the component/route/service/pipe of that directory.
I think that’s it for this.
Issue Analytics
- State:
- Created 8 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Code Style Guide - Drake
This section defines a style guide which should be followed by all code that is written in Drake. Being consistent with this style...
Read more >Content style guide: A step-by-step guide to creating your own
Get a step-by-step guide to creating a content style guide for your brand to create better, more consistent content.
Read more >Google Python Style Guide
This style guide is a list of dos and don'ts for Python programs. ... Decorators should follow the same import and naming guidelines...
Read more >API Style Guides | Guidelines + Best Practices - Stoplight
This API style guide reference gives an overview of API guidelines, what they are + best practices to create, use & enforce them...
Read more >Style guide - Advanced R. - Hadley Wickham
Good style is important because while your code only has one author, it'll usually have multiple readers. This is especially true when you're...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
At the current state of the project (pre-alpha) I think we can make changes without documentation in place. Especially given our milestone goals.
Hi @hansl. Would you have a link to the repo mentioned?