You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 25, 2023. It is now read-only.
* connects features which have attached relation to parent module
77
+
* connects features which have attached relating to the parent module
78
78
*
79
-
* about module has its own routes which we wanna connect
79
+
* about module has its routes which we want to connect
80
80
*/
81
81
connectFeatures<AppNotes>(APP_NOTES_KEY, {
82
82
about: aboutUnit
83
83
});
84
84
85
85
/**
86
86
* Routing module contains its configuration
87
-
* and providers (resolvers, guard, interceptors etc)
87
+
* and providers (resolvers, guard, interceptors, etc.)
88
88
*
89
89
* Exports RouterModule
90
90
* and NavigationModule for navLink directives
@@ -120,7 +120,7 @@ export class HeaderComponent {
120
120
121
121
//or
122
122
123
-
// getting unit by name
123
+
// getting the unit by name
124
124
@Secluded('app')
125
125
public app:Unit<AppNotes>;
126
126
@@ -142,10 +142,10 @@ You can find a more complex example in this [repo](https://github.com/maktarsis/
142
142
Routeshub offers an approach (pattern) to structure routing in the application. You can explore it in this [repo](https://github.com/maktarsis/routeshub/tree/master/example-app).
143
143
144
144
**Guideline**:
145
-
- Each module in application has a hub directory
146
-
- hub directory contains three files that configure routing of the current module
@@ -165,10 +165,10 @@ There are two ways to create the `unit`:
165
165
166
166
Each creator takes the `routes: Routes` and an object of options
167
167
- key - unit identifier and accepts string or symbol
168
-
- routeName - accepts an object with optional custom names for wildcard ('**') and root ('') paths
169
-
- nearby - accepts lazy units (**connectors**) which are outputs of **feature creator**. Nearby option should be used when one or more connected features are eager modules with their own routes files.
168
+
- routeName - accepts an object with optional custom names for a wildcard ('**') and root ('') paths
169
+
- nearby - accepts lazy units (**connectors**), which are outputs of **feature creator**. A nearby option should use when one or more connected features are eager modules with their own routes files.
170
170
171
-
**Root** creator invokes only once to initialize the hub in the application. `createRoot` takes initial `appNotes`
171
+
**Root** creator invokes only once to initialize the hub in the application. `createRoot` takes initial `appNotes`.
172
172
173
173
**Usage example**:
174
174
```typescript
@@ -179,7 +179,7 @@ Each creator takes the `routes: Routes` and an object of options
179
179
});
180
180
```
181
181
182
-
In turn, the **feature** creator is responsible for creating lazy units (**connectors**) which should be connected to the parent unit
182
+
In turn, the **feature** creator is responsible for creating lazy units (**connectors**), which should connect to the parent unit.
0 commit comments