Angular Mysterious Routing

-

 I was working on an Angular app and one fine day I imported a module into another module. After doing so I noticed that the routing on my importee ( or whatever tf it's called ) is not working and it is replaced by the routing , of the imported module. 


After wasting a few good minutes I found out that the reason for this mysterious behavior is the ORDER in which you import these modules. If you import the imported module before the routing module of your importee module , then the visitor's routing will take over yours. 


Following screen shots explains this with sample modules. The file shown here is the innocent.module.ts  which is my importee. ImportedModule is the imported module.


OK

This order is OK as the InnocentRoutingModule is imported before ImportedModule . All good!





NOT OK

This order is NOT OK as the InnocentRoutingModule is imported after ImportedModule . Imported module routing will therefor take over , bad Angular bad ! 




So that's it guys ! Be mindful of the order you import stuff , that is the key takeaway ! Cheers ! 

Comments

Post a Comment

Popular posts from this blog

Wasted about an hour of my life on something so trivial

-
Image
 Ok guys so i wasted about an hour trying to figure out how to bind to the "disabled" property in a textbox in angular. And after trying for a long time i realized that my code is not working as expected because , you have to use null instead of "false" to control it. Please refer to the stackoverflow answer below. Darn it ! https://stackoverflow.com/questions/42179150/how-to-disable-a-input-in-angular2/43765804
Read more

OneNote Code Format plugin

-
If you are using OneNote like me to keep your shit together and ever wondered why this does not have a built in code formatting option, then your worry days are over. No one wants to see their code lying around without formatting in plain text form , so make use of this plugin to make things prettier. https://www.makeuseof.com/tag/programmer-onenote-coding-add-on/ 
Read more

With Values

-
Image
 Using the clause WITH VALUES when you are adding a new column to an existing table using Microsoft SQL Server is a handy little trick. The use of WITH VALUES is when you want to add a default constraint to an existing table that allows null . Because when you add a default constraints that allows null it will NOT fill the existing rows with a value, this can effect your database logics ( if you have written some code depending on these values ).  Let me demonstrate this with some simple tables. Create a simple table CREATE TABLE Students( id int NOT NULL, name varchar(50) NULL ) Add some sample data insert into Student (id,name) values (1,'Cappadonna'), (2,'UGod') Add a new column to the table , with NOT NULL  clause ALTER TABLE Student ADD age int not null CONSTRAINT age_default DEFAULT 99 Now if you query your table you will see that the existing rows are being populated with your default value. This is because we added the constraint as NOT NULL.    Now let
Read more