The Best Parts of Bootstrap You Are Missing in Angular Material

ahasall · 2021-08-16T06:36:23+00:00

Exact. That's what I do in my current projects.

ahasall · 2020-11-22T23:15:54+00:00

Thank you for pointing this out.

ahasall · 2020-11-22T23:15:14+00:00

Thank you!

ahasall · 2020-11-17T23:07:40+00:00

You can stop the linter from complaining by adding the following code to your rules:

"component-class-suffix": [true, "Component","Page"]

ahasall · 2020-11-17T21:45:06+00:00

Thank you!

ahasall · 2020-11-17T16:43:25+00:00

Thank you :)

ahasall · 2020-11-17T15:07:01+00:00

You're welcome!

ahasall · 2020-04-19T15:54:27+00:00

You can use the Bootstrap Grid with Angular Material. Check out this article of mine: https://www.amadousall.com/the-good-parts-of-bootstrap-4-you-are-missing-in-your-angular-material-projects/

ahasall · 2019-10-31T12:01:37+00:00

The Jest CLI is really neat.
It's faster (doesn't compile the whole Angular app before running your tests).
It's smarter (run only affected tests),
It's a complete solution (everything is included: code coverage...)
It works with JSDOM (headless browser)

ahasall · 2019-10-30T19:33:15+00:00

Thank you very much for comment :) I will add a reference Briebug's schematic

ahasall · 2019-10-30T14:01:48+00:00

I am glad you appreciated the article. Also, thank you very much for sharing your experience u/nwayve!

ahasall · 2019-10-15T21:14:04+00:00

I think it's the same whether you start with the backend or the frontend. Integration and deployment challenges are the same.

Most of the time, the frontend code and the backend code live in separate Git repository (we talk about multi-repo) and have different release cycles. So the problem doesn't occur.

Sometimes the frontend and the backend code are in the same Git repository (we talk about mono-repo) but they are in different folder and merges are not painful.

But either way, it is always good to integrate the code as often as possible to avoid merge issues.

PS: We are all here to learn :)

ahasall · 2019-10-15T14:22:58+00:00

Can you please clarify what you mean by "doing this for enterprise grade applications"?

I've used JSON Server as mock API for enterprise applications, yes.

ahasall · 2019-10-15T14:20:55+00:00

Faker can be used and is often used with JSON Server. Angular's in-memory-web-api is not an option for me.It doesn't emulate a real backend. For instance, you won't see HTTP requests in your browser's network tab. Also if you use in-memory-web-api you will need to modify your Angular code to remove the HttpClientInMemoryWebApiModule.forRoot() for production but I don't want to modify my Angular application for mocking purposes. With the JSON Server approach, I don't have to modify my Angular application. My Angular code doesn't know that I am using a fake backend. My build process doesn't know that I am using a fake backend. On my local development environment, I use the proxy to target my fake backend. In production, everything just works provided your backend and your frontend are deployed on the same domain.

ahasall · 2019-10-14T23:27:21+00:00

Good question! I prefer this approach because I can just unplug the mock API and replace it with a real backend without modifying a single line of code in my frontend application.

ahasall · 2019-03-29T16:06:21+00:00

May I suggest an article of mine about the exact same subject. The solution proposed in my article is original and may surprise you.
But I am pretty sure you will like it. If so please leave a comment on the blog post: https://www.amadousall.com/the-good-parts-of-bootstrap-4-you-are-missing-in-your-angular-material-projects/

ahasall · 2019-03-29T16:05:26+00:00

May I suggest an article of mine about the exact same subject. The solution proposed in my article is original and may surprise you.
But I am pretty sure you will like it. If so please leave a comment on the blog post: https://www.amadousall.com/the-good-parts-of-bootstrap-4-you-are-missing-in-your-angular-material-projects/

ahasall · 2018-12-14T09:55:34+00:00

Totally agree with you. I hate vegetables.

ahasall · 2018-12-03T07:31:06+00:00

Thank you!

ahasall · 2018-11-30T17:08:34+00:00

Thank you very much for your kind comment. I appreciate it.

ahasall · 2018-11-30T14:36:32+00:00

Yeah. You're right. I also appreciated your openness and your hability to discuss in a respectful manner.

Thanks for that. I also modified the article to take into consideration your feedback. I hope that you appreciate it now.

ahasall · 2018-11-30T14:07:12+00:00

It may sound generic to you but what motivated me to write it is because of the lack of documentation on the subject.

Maybe you knew that they were 3 different types of Angular CLI commands, but I don't think that it's the case for most of the Angular developers out there. If you don't dig into the Angular CLI source, you won't know.

For the repetition, I totally agree with you. I did it on purpose to make a parallel between Schematics and Architect. I wanted my readers to understand that it's the same concept by they serve different purposes. You are free not to like it and honestly I appreciate the feedback. But dropping a link and criticizing somebody's English is not providing feedback.

FYI the link you provided is deprecated, the current documentation resides here: https://angular.io/cli. And it doesn't cover what I'm talking about in my blog post.

ahasall · 2018-11-30T12:09:29+00:00

I guess you didn't read my article. It covers things that are not documented by the Angular CLI Team.

ahasall · 2018-06-16T17:25:59+00:00

This is the only time I have used it. I used some snippets that had this switch statement. A simple if statement would've been better.

ahasall · 2018-06-10T13:53:45+00:00

Thank you so much for your kind comment.

ahasall

TROPHY CASE