<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Natalia Venditto on Medium]]></title>
        <description><![CDATA[Stories by Natalia Venditto on Medium]]></description>
        <link>https://medium.com/@nataliafrontend?source=rss-175f90e7c76d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*IjJ-rcn8B3XGA0sAukLUkg.jpeg</url>
            <title>Stories by Natalia Venditto on Medium</title>
            <link>https://medium.com/@nataliafrontend?source=rss-175f90e7c76d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:31:48 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nataliafrontend/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Deploying an Angular 9 site to Netlify with netlify CLI]]></title>
            <link>https://medium.com/@nataliafrontend/deploying-an-angular-9-site-to-netlify-with-netlify-cli-8206b8c1dad?source=rss-175f90e7c76d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8206b8c1dad</guid>
            <category><![CDATA[angular-9]]></category>
            <category><![CDATA[ci]]></category>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[netlify]]></category>
            <category><![CDATA[angular-cli]]></category>
            <dc:creator><![CDATA[Natalia Venditto]]></dc:creator>
            <pubDate>Sat, 15 Feb 2020 01:49:57 GMT</pubDate>
            <atom:updated>2020-02-15T08:46:39.739Z</atom:updated>
            <content:encoded><![CDATA[<p>I wrote a previous post on <a href="https://medium.com/@nataliafrontend/upgrading-from-7-0-4-to-angular-9-a-true-use-case-207d07c0922a">how straight forward it was to migrate from version 7.x.x. to version 9</a>, using the inbuilt automated update in the Angular CLI.</p><p>To elaborate more on this mechanism, it basically upgrades you using the target version of the CLI, so you have all the latest features available from the get-go.</p><p>What I wanted to do next, was to deploy the site live, somewhere. A few days ago, I created a <a href="https://www.netlify.com/">Netlify</a> account. Netlify is a pretty cool platform to develop, build, release and host your sites, and offers you a basic free account with the benefit of putting a site to prod at no cost.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y6bhLUYPo-dILXsF0A7gmw.png" /><figcaption>Updated app to Angular 9</figcaption></figure><p>The first thing I did was to republish the updated site to a new Github repo. Once there I had to link this repo to Netlify, and give some permissions for it to be deployed to Netlify.</p><p>Netlify offers deploys via CI (continuous integration), a UI in their own platform, or CLI. I decided to test all three options. The UI is pretty straight forward and you will have to use it to configure deployment even from the CLI. Deploying is only a click away.</p><p>But if you’re used to the terminal, you for sure want to install the Netlify CLI. For that run</p><pre>npm install netlify-cli -g &amp;&amp; netlify login</pre><p>It will install the package and also guide you through authorizing the Netlify app to your Github (or other repo hosting service, I think I saw GitLab and bitbucket on the list).</p><p>Once there, and after having configured your deploy command, typically</p><pre>ng build --prod</pre><p>and distro path, typically</p><pre>dist/[your-app-name]</pre><p>you will be allowed to execute</p><pre>netlify deploy (or netlify deploy --prod)</pre><p>to build and deploy your angular site.</p><p>Something that can be improved is the logging: I had a misconfigured path and the build was failing, but I was not getting input whatsoever. I knew something was wrong after 17 minutes, but what?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vdKcSbHt0vZFctkhu1bFRQ.png" /><figcaption>Waiting for deploy to go live after 17 mins…</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LytFZI0hZofc9M6tsi-w7g.png" /><figcaption>No log on build fail.</figcaption></figure><p>I decided then to do some changes in the code and push, so I could see continuous integration working. When I did that, I got a log and could understand and fix the error. Finally, after a couple of attempts, my site was live!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z7Dn2zXhjoNee7qpIW6-Hw.png" /><figcaption>The site finally deployed to Netlify, after 4 and a half minutes.</figcaption></figure><p>The build + deploy time is a bit high for an app these characteristics. And I will try to optimize that, while I tell you about it, in future posts.</p><p>Thanks for reading!</p><p><em>PS: I got an email from Netlify letting me know I had a mixed-content issue on the site. I knew that. But it even explained in what API call. So I could fix it in 1 minute, push to Github, and closed the computer, sure that the CI agent (at work I work with Jenkins) will do its job.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8206b8c1dad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Upgrading from 7.0.4 to Angular 9 a true use case]]></title>
            <link>https://medium.com/@nataliafrontend/upgrading-from-7-0-4-to-angular-9-a-true-use-case-207d07c0922a?source=rss-175f90e7c76d------2</link>
            <guid isPermaLink="false">https://medium.com/p/207d07c0922a</guid>
            <category><![CDATA[angular-9]]></category>
            <category><![CDATA[angular-update]]></category>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[ivy]]></category>
            <dc:creator><![CDATA[Natalia Venditto]]></dc:creator>
            <pubDate>Fri, 14 Feb 2020 21:53:21 GMT</pubDate>
            <atom:updated>2020-02-15T08:45:07.668Z</atom:updated>
            <content:encoded><![CDATA[<p>I happen to be an organizer for <a href="https://twitter.com/wtmbcn">Women Techmakers Barcelona</a> International Women’s Day. Any event of that size (200 attendees in 2019, nearly 80 submissions to the c4P this year), needs a website. I volunteered to create and maintain the website last year and, of course, I did it with Angular. At that time the version of the CLI I had installed globally, was 7.X.X and that’s the version we have until today.</p><p>I don’t think I will migrate the site effectively today, because we’re amidst the organization and there is so much going on! But I wanted to use it to test the new automated upgrade capabilities of Angular 9 CLI and the Ivy compiler after the upgrade.</p><p>The repo is hosted in Github and published on Github pages and has a redirection to a GDG domain, and it very much serves its purpose, I was not thinking it was a priority to update it. However, I think it can be used as a tool for experimentation.</p><p>Let’s see how this implementation gets or not straight forward updated via the CLI. First things first. Let’s check what’s the current global version for angular CLI I have on my computer.</p><p>The first thing to do is to fork a copy of the repository and then verify the versions installed.</p><p>We do that by running</p><pre>ng --version</pre><p>that will give us a lot of information, including the node version we’re running at a global level. For me, this was the output.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8qW6MY7EQRSW0geTxH35Dw.png" /><figcaption>Checking your current version of Angular CLI, globally</figcaption></figure><p>Looks like there is a lot to update here!</p><p>But is this something we want to override at a global level? Not so sure of that! I ran several applications, some at work, and that combo of node 10.11.0 and Angular 7.x.x., is doing its job well! Let’s do it locally instead!</p><p>First of all, I was curious about what would happen if I did effectively run the commands</p><pre>ng update @angular/cli @angular/core</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KAGUJTYdc_nPZIdQjY7zlA.png" /><figcaption>Results of executing update without a version target</figcaption></figure><p>Of course, I was expecting something like this. I still have to investigate what the `packageGroup metadata of package angular/cli is malformed` , means.</p><p>But let’s do the regular procedure and, in the same way as I have already multiple times advised to go when having to upgrade an angular app (especially if the size is large), upgrade to a most immediate version, instead. In this case, I will go directly to version 8, because I am interested in experimenting on how straight forward this can be.<strong> Please remember I am doing this on a copy, of a versioned repository. </strong>So if it breaks, it’s not a big deal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e7aUpPxcqreMFN7VSMxc_A.png" /><figcaption>Result of updating to the next major version, in this case, 8.x.x</figcaption></figure><p>Can we now go from 8 to 9 with the update command? Let’s try.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qwfD6GlnOxAN18SNOGLCxQ.png" /><figcaption>Angular update mechanism to version 9, needs node v10.13 o v12.0</figcaption></figure><p>Oops, the first thing to notice is that this update requires node 10.13 or 12.0 at a minimum. And remember I had 10.11.0 globally, so I will need to upgrade that first. I can do that locally with nvm</p><pre>nvm install 10.13.0</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-6Eb2eHlYx9B9Qk7ck98VQ.png" /></figure><p>Let’s now try again! But first, I had to reinstall all the packages because I was in a new version of node! When you install a new version of node locally, you need to install angular and the CLI globally for this version. Once done, you also need to run `npm install` to install all the dependencies.</p><p>Now we’re ready to finally do the upgrade. Will it work?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1wsI39ZfkipLw8xqUeRmqg.png" /><figcaption>Angular 7.0.3 updated to Angular 8, to Angular 9</figcaption></figure><p>Yes! Now it worked and also I am getting a log of potential issues, like an incomplete provider definition, and undecorated class, or the automatic migration of Renderer to Renderer2. I am a bit afraid of all that and what will happen when I try to serve this locally. Let’s see…</p><p>The good part is it did compile without errors (after removing a module I was importing, that no longer was available.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*np41rF-TuPEqDoznRdYEvQ.png" /><figcaption>Compilation and build successful!</figcaption></figure><p>What about now, will I be able to serve this?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D4iv7wff2AZr8uJSQ-Q9OA.png" /><figcaption>Just WOW! It works!</figcaption></figure><p>Amazing. Everything is working as expected! That was definitely straight forward. I may definitely migrate the live version after all! That can give me information to share, on how well it plays with Github pages.</p><p>For now, I will write the next article, <a href="https://medium.com/@nataliafrontend/deploying-an-angular-9-site-to-netlify-with-netlify-cli-8206b8c1dad">deploying this application to Netlify</a>, and getting some metrics on performance, as a form of comparison.</p><p>Thanks for reading!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=207d07c0922a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Effective automated scaffolding with Angular Schematics]]></title>
            <link>https://medium.com/angular-in-depth/effective-automated-scaffolding-with-angular-schematics-c61d6640b7d5?source=rss-175f90e7c76d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c61d6640b7d5</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[schematics]]></category>
            <category><![CDATA[angular-cli]]></category>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Natalia Venditto]]></dc:creator>
            <pubDate>Thu, 14 Feb 2019 12:46:00 GMT</pubDate>
            <atom:updated>2020-04-29T21:22:45.952Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*iNd-M-FtV-gyAMiUx7q-dQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/743/0*uMdg4L9K3ioEzbfY.png" /></figure><blockquote><a href="https://medium.com/angular-in-depth"><strong><em>AngularInDepth</em></strong></a><strong><em> is moving away from Medium. More recent articles are hosted on the new platform </em></strong><a href="https://indepth.dev/angular/"><strong><em>inDepth.dev</em></strong></a><strong><em>. Thanks for being part of indepth movement!</em></strong></blockquote><p>Recently I spoke at <a href="http://www.frontenddeveloperlove.com/">Frontend Developer Love</a> about Angular Schematics as a solution to avoid common pitfalls and bad practices when architecting and coding an Angular app. In combination with the Angular-CLI, Schematics becomes a powerful tool to define your project structure, and make sure you can replicate it across many workspaces.</p><p>Let’s start by defining the <strong>problem</strong>. Whether you’re a freelancer, work at a small agency, or are a member of a large organisation, it is likely you’ve come across this scenario: you or your tech lead, or the architect at your project have finally found the right project structure, best practices for dependencies, naming and other conventions you want to be followed by everyone developing Angular projects in your company -or even yourself in the future, if you’re working as a contractor- but, documenting and passing quality gates, becomes an arduous AND expensive job.</p><blockquote>In the end, you end up copy-pasting a lot of boilerplate, searching and replacing ID’s in your IDE, manually adding or removing chunks of code or writing the structure folder by folder, file by file. Let’s agree that’s not the most productive way of getting things done.</blockquote><h4>Project structure</h4><p>Yesterday I wanted to have everyone on the same page when it came to understanding the concept of a well organised and meaningful project structure. So I described it with this image.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y4-BlO2bKB2baKcT5dOGCA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/REy_bjC0Lcw?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Michael Eggerl</a> on <a href="https://unsplash.com/search/photos/structure?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>We have to design our project structure just like the person that designed that window carefully drafted it, to connect each element. They probably very consciously chose the materials, the width and weight, and placed each item strategically, including the steps so you can easily maintain that window clean.</p><h4>Let’s propose a more concrete problem to solve</h4><p>Let’s suppose, in this case, that we are pretty sure what’s the folder structure to accommodate our <strong><em>.scss</em></strong> files should look like, but we don’t want to:</p><ul><li>write the structure by hand, adding each folder and file manually</li><li>have to write long relative paths in order to import and resolve our common files as dependencies to other <strong><em>.scss</em></strong> code</li><li>we definitely don’t want to be copying and cleaning from a different project!</li></ul><h4>Let’s now use schematics to turn all this manual work, into magic</h4><p>First of all, we need to make sure we have the right node version -latest LTS is fine-, that will allow us run Angular-CLI and Schematics. We also need to globally install the following dependencies in our system, before we start</p><pre>+ @angular/cli<br>+ @angular-devkit/core<br>+ @angular-devkit/schematics<br>+ @angular-devkit/schematics-cli<br>+ @schematics/schematics <br>+ rxjs</pre><p>Once we have our global dependencies installed, we can create our first blank schematics, by running the command below (please notice that I’m passing <strong><em>my-schematics</em></strong> as name, but you can pass whatever your schematics name may be)</p><pre>$ schematics blank --name=my-schematics</pre><p>That will create a blank schematics in your system. From where you can start writing your schematics. You can either delete now that schematics, or you can just rename the <strong><em>RuleFactory</em></strong> name, and continue from there.</p><h4>Wait. The RuleFactory? What’s that?</h4><p>Each schematic is basically a <strong><em>RuleFactory, </em></strong>that means it is a function that takes options as arguments, inputs a <strong>tree </strong>(or <strong><em>source</em></strong>, in the case there is nothing in the tree yet), applies whatever <strong><em>Actions</em></strong> you <strong>describe</strong> and outputs another tree. Each schematics has a <strong><em>schema </em></strong>to validate it, and it’s part of a <strong><em>collection</em></strong>. I know that’s a lot of vocabulary, there. And please notice that I also made “describe” in bold letters. And I will explain why.</p><blockquote>Schematics are in the end a descriptive generators that work as a transformation pipeline. And the best part is that, although you can pipe them or chain them together, they are atomic, extensible and reusable.</blockquote><h4>Generators? What are generators?</h4><blockquote>Code generators are tools that actually generate other code, templates, etc, on a command prompt. You may have heard of Yeoman, or Maven Archetype, etc.</blockquote><p>Let’s go through the important vocabulary you need to acquire, to better understand schematics as generators</p><ul><li><strong>collection</strong>: a definition of our schematics. If your schematics are not part of this object, they won’t run.</li><li><strong>schema</strong>: the object that validates our schematics input and description</li><li><strong>./files (tree or source):</strong> a virtual file system and its metadata that serves as a staging area</li><li><strong>Rule</strong>: a function that takes a tree in and outputs another tree (typically after you applied some Actions)</li><li><strong>RuleFactory</strong>: a factory for rules, it takes options as arguments (the ones you pass via the command line)</li><li><strong>Action</strong>: an atomic action that transforms your tree in one way or another</li></ul><p>This actions are methods of the Tree interface. There are methods to access or <strong>visit </strong>your file system, to <strong>read</strong> the content of files in it, to <strong>move</strong> directories or files from one location to another, but the four more important functions that have the potential to modify your file system, are</p><ul><li>create</li><li>overwrite</li><li>delete</li><li>rename</li></ul><p>I think the names are pretty self-explanatory, so I won’t go into detail. But what I would like to stress is the descriptive nature of schematics. This means everything you’re writing in your factory, <strong>is purely descriptive</strong>. And schematics, when ran from the schematics project itself, is always a dry-run. Which means that unless you explicitly pass this flag</p><pre>--dry-run=false</pre><p>your file system will remain intact. So you can test your schematics, atomically, and only commit those changes to your tree (stage) when you’re ready!</p><p>Watch out, though! If you execute them from your Angular project with</p><pre>ng generate .my-schematic:my-schematic --options</pre><p>you’re definitely going to modify your file-system. If you’re using a version control system, you probably don’t have a lot to worry about. But you have to be aware of this!</p><h4>Anatomy of a schematics RuleFactory</h4><p>Let’s take a closer look at what one of those rules factories look like, and what they can do. For that, I am embedding this video. As you can see, that’s the schematics generated when creating the blank schematics. I pass the _options.name as name to a file I want to create, I pass an alternative name as string, and the content of the file as string, too. As you can see, the first time I run the schematics, nothing happens. The second time, however, I do add the — dry-run=false flag, and my file system is altered.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FHMQnnbGlPjU%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DHMQnnbGlPjU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FHMQnnbGlPjU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/8b84bbdfa7c031996e15f5b8a30c74dd/href">https://medium.com/media/8b84bbdfa7c031996e15f5b8a30c74dd/href</a></iframe><h4>What is the schema.json for each schematics and how does it help?</h4><p>Instead of writing a lot of words here, about the schema and why it’s important, I am pasting a gist with some annotations. Obviously, you save a lot of time in writing exceptions handling, by using the validation schema.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/4dad7bc3019faff424e8be28c2263c15/href">https://medium.com/media/4dad7bc3019faff424e8be28c2263c15/href</a></iframe><p>I invite you to fork the demonstration repository from github, <a href="https://github.com/anfibiacreativa/frontendddevlove-angular-schematics">https://github.com/anfibiacreativa/frontendddevlove-angular-schematics</a> and start playing with it. You have all the instructions in the readme file, on how to get it up and running, before you keep reading.</p><h4>The template definitions, or how you actually create the structure ONCE</h4><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FHMQnnbGlPjU%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DHMQnnbGlPjU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FHMQnnbGlPjU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/8b84bbdfa7c031996e15f5b8a30c74dd/href">https://medium.com/media/8b84bbdfa7c031996e15f5b8a30c74dd/href</a></iframe><p>If you take a look at the above embedded video, you will see I am creating indeed a folder structure manually. But this operation is performed <strong>only once</strong>. Further more, it is a lot more than just creating a few folders and files. I am actually defining instructions on what the names should look like, and even the content! Everything after two dashes is defined dynamically as described in your schematics. In the case of the video, I am:</p><blockquote>indicating the path where the structure should be created at, that is passed as _options.path, and then creating a folder below that will be called after a dasherized string of whatever I pass as _options.name. dasherize() comes with a set of utilities or helper functions inbuilt in schematics. You have a lot more options. But you can also chain your own custom functions and they will be applied to your templates!</blockquote><p>I will address here some of the valid questions I’ve got after the talk last evening, they may be relevant for you, too:</p><p><strong>1.Why don’t you have the schematics project as a module inside of your angular project?</strong></p><p>Separating concerns is always a good idea. When you separate your code this way, it’s more maintainable, specially considering that the schematics will become a dependency to whatever Angular projects you have linked to it.</p><p><strong>2.Can I have several Angular projects, or even workspaces, linked to a same schematics project?</strong></p><p>Absolutely. And you should. That’s the most important principle of making use of this pattern. The idea of repeating yourself the less, keep dependencies to a minimum, have to maintain the least code, and reuse it whenever possible.</p><p><strong>3.In the time it takes to write a schematics scaffold, I could’ve copied a project several times. Why is this a better option?</strong></p><p>Absolutely, you could. But would it scale? What would be the maintenance efforts, the documentation efforts, and the ramp up times for new members of your team in the future. Additionally, you only got to perform a quality gate for that particular process once, when you commit your schematics code. You don’t have to engage in large arguments and back and forth over less relevant problems, or style.</p><p><strong>4.Doesn’t it get even more problematic as the projects scale. Won’t it create unwanted stuff where you don’t need it?</strong></p><p>It may. You need to pay careful to the design of your schematics. Does this pattern suit all cases? Probably not. But what pattern does? There may be a time when a particular schematics does not work anymore for every one of the projects linked. But that’s the coolest part. Since you can pass a schematics to another schematics, to another schematics, over and over, you may want to try writing the smallest, most atomic action in each one of them. That’s a good practice anyway, to preserve single responsibility.</p><p><strong>5.What was the tune you walked in the stage with?</strong></p><p>Repeat after me… No, that’s the tune. Guess why?</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FNdgSBW6XX1I%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DNdgSBW6XX1I&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FNdgSBW6XX1I%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/814793ebb9a713d8b8ed7810104e3c04/href">https://medium.com/media/814793ebb9a713d8b8ed7810104e3c04/href</a></iframe><h4>To sum it up</h4><p>I presented a quite frequent problem, and solved it in a simple way by creating routines via schematics, that will modify your angular configuration files to:</p><ul><li>create an ideal folder structure that you can replicate over and over at your project setup phase, without any manual effort.</li><li>generate an alias to import your class members in an easy way</li><li>easily import <strong><em>.scss</em></strong> files without having to write complex relative paths</li></ul><p>Of course, there are a lot more complex stuff you can do with Angular Schematics. In the end, everything you generate through the Angular-CLI is implementing Schematics under the hood.</p><p>I truly believe this is a <strong>must-use</strong> tool for every Angular developer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c61d6640b7d5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/angular-in-depth/effective-automated-scaffolding-with-angular-schematics-c61d6640b7d5">Effective automated scaffolding with Angular Schematics</a> was originally published in <a href="https://medium.com/angular-in-depth">Angular In Depth</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>