-
Notifications
You must be signed in to change notification settings - Fork 556
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OPINION #52
Comments
I actually like this idea. I think we're going to see a lot of angular specific libraries follow this convention. |
Nice ! 👍 |
@pkozlowski-opensource @johnpapa @gdi2290 @robwormald Can you guys help us in this decision. Thanks in advance 😄 |
|
@gdi2290 I saw even material2 started using @
Just wondering if the angular team is going to get rid of @ in the future releases or whats the reason you don't want formly to use @. Thanks 👍 |
yeah I think you're looking for something like |
I want this to be able to render on the server/webworker so it would also be great if you separated the platform logic and interacted with the renderer directly |
i wouldn't do this just for the sake of it, unless you really have a need to break out into smaller packages that are functionally independent - it's a non-trivial amount of work managing the process. It makes sense for things like @ngrx or @Material because they have a number of independently functional components or services, that can be independently distributed. I'm not saying don't, just... consider if you really need to do this. |
I think it makes sense for our repo to have separate functional components, since we want to have templates are separate, and again the templates could be of bootstrap, ionic, material2 or any other. Thanks a lot |
To publish with @, npm will require us to make an organization which is paid on npm, so I think we should think about something else instead 😭 |
I am thinking about
or
or
or
|
I would prefer something like
all templates could go in the I'm still pretty new to publishing things on NPM but couldn't we follow the same structure you had planned without the |
I think we should rename our publishing to npm like how angular team did it.
Instead of importing like
to
Any other opinions/comments/suggestions
@divyakumarjain @micouz @TheMcMurder @mathijshoogland
The text was updated successfully, but these errors were encountered: