content(typescript): use path mappings to simplify imports#21
content(typescript): use path mappings to simplify imports#21bovandersteene wants to merge 1 commit intotypebytes:masterfrom
Conversation
content(typescript): use path mappings to simplify imports
|
Hey Bo, Thanks for the submission! |
|
Hey @bovandersteene and @KwintenP, I agree that there are a few edge cases for when path mappings would make sense. It's quite delicate and for libraries I absolutely agree, e.g. for libraries that the Angular CLI or Nx create. But for just shortening paths in your application I think it's not a good idea to introduce math mappings. But then again, if you treat your folders inside your app as "libs" then it could make sense again. So I think it's not that clear when to use path mappings. But this is just my personal opinion. We can for sure discuss this. |
|
Hey @bovandersteene, what do you think about our comments and the comments from the community in the link @KwintenP posted? I am curious what you think about this and whether it makes sense to add such item to the checklist. |
|
This is what worries me a little in adding this item. I think it is quite hard to get that message out correctly so that everyone will properly get this. Do you think it is best not to add it in that case @bovandersteene and @d3lm? |
|
@bovandersteene @KwintenP I think this is a good practice and we should go forward with this PR. For Angular apps it makes sense to use path mappings, whereas for node it could cause some issues. I have also asked around on social media and most people agree that path mappings are / should be a best practice that projects should follow. |
|
@d3lm I think we should go forward with this |
content(typescript): use path mappings to simplify imports