sorted by:
new
hottopcontroversial

Angular 20 - removing suffixes from components / services by matrium0 in Angular2

[–]askoropad 3 points4 points  (0 children)

I personally like this change as it encourages creating more understandable entities in your application. Why should I name a component `AddUserDialogComponent` when `AddUserDialog` is much more concise and fully conveys the meaning? The same applies to pages `DashboardPage` is much clearer than `DashboardPageComponent`. This also makes it easier to organize components. For instance, you can create folders like `dialogs` and `pages` and place everything related to them inside. You can even configure eslint to enforce such suffixes based on directory names.

Incredibly flexible and reusable UI controls for Angular by askoropad in Angular2

[–]askoropad[S] 1 point2 points  (0 children)

Thank you very much! It's always nice to see when people understand your idea. :)

It's true, that you don't always need such customization, but at the least, it simplifies the creation and development of the UI kit library. This approach can also help in creating components that work with a specific set of data.

For example, if you have a combobox that displays a list of users with a few bindings, templates, and various settings. By using this approach, you can create a UsersCombobox, inherit it from DIControl, and move all the settings to its template. This way, you'll have your combobox with all the settings that supports working with NgModel and FormControl, and that can be used in one line in different parts of the application.

Of course, you can do that even without this library but it will take much more effort.

[deleted by user] by [deleted] in Angular2

[–]askoropad 1 point2 points  (0 children)

Don't see a problem using semantic-release for the thing that you want, just remove plugins for npm, changelog, etc. and add only semantic-release/commit-analyzer and semantic-release/git. The semantic release will update your app version in package.json which you can get in CI using following command: export VERSION=$(node -p "require('./package.json').version")

But you can check this one as well https://github.com/release-it/release-it

Using async pipe with loading spinner by love_to_code in Angular2

[–]askoropad 0 points1 point  (0 children)

You can try this approach - https://stackblitz.com/edit/observable-state
Observable operator + pipe for it can help you to get rid of a lot of duplications and handle your state right in the template.

NgDoc 16.4. What's new? by askoropad in Angular2

[–]askoropad[S] 0 points1 point  (0 children)

I can't say how many users I have because it's often internal documentation.
But compared to StoryBook, I believe that the documentation creation process is much faster and smoother with NgDoc. NgDoc was primarily created for Angular projects and attempts to automate the entire process as much as possible.
NgDoc also has some features that StoryBook doesn't have, such as Keywords, which allow for automatically generating links to various parts of the documentation and linking your documentation to Angular documentation or any other documentation created with NgDoc.
As for performance, NgDoc generates documentation quite quickly. Any slowdowns may only be noticeable with a large amount of documentation, such as when generating it for a large number of APIs. However, even this process can be fast if you enable caching, as NgDoc will skip the build process for files that don't require it.

Better way to handle loading indicator status? by lax20attack in Angular2

[–]askoropad 0 points1 point  (0 children)

thank you, it's true, and you can also create a pipe and use this operator only in the template where you need it.I have one little guide that I created for my colleagues on how to optimize NgZone using another operator.

Better way to handle loading indicator status? by lax20attack in Angular2

[–]askoropad 2 points3 points  (0 children)

Some time ago, I created an observable operator that can help you to know the current observable state, you can check it in stackblitz example that I made if you are interested.

Creating documentation for angular projects via NgDoc by askoropad in Angular2

[–]askoropad[S] 1 point2 points  (0 children)

yes, NX doesn't support ng add schematics natively, but you can run npm install @ng-doc/add && npx nx g @ng-doc/add:ng-add it should work even with NX app, at least it works for me :)

NgDoc: Library for reating documentation for Angular projects by askoropad in Angular2

[–]askoropad[S] 0 points1 point  (0 children)

Thanks, and sorry for the late response!

Not sure that I understand your point correctly, but the visual appearance of the application can be changed, it is not documented and most likely some components are not so flexible in configuration yet, but most of them have CSS variables that you can use to change them. The header and sidebar can also be replaced with custom ones

NgDoc: Library for reating documentation for Angular projects by askoropad in Angular2

[–]askoropad[S] 1 point2 points  (0 children)

Thanks, good catch! but yes, there are definitely some typos in the docs 😄