Understanding the routing in the app was complicated for me esp for instances like the Resources app.
The dead-ends I tried in order to route to crop-probability were:
Creating a resource type for components that required routing, this was added to the resources model.ts file. Then I created a component resource in the crop data file to be rendered as a child of the Crop, Pest and Disease resource type. But I think those are auto generated using a certain command since each had a _key and _timefields for creation and modification. This would have made it easy to route to the component on click.
Also tried "hard-routing" through the resources page but there were complexities due to how the resource items are represented.
For the crop icons:
When rendering the custom icons, the assets URL is not appended correctly. Is that attributed to the routing implemented?
Description
Discussion
Understanding the routing in the app was complicated for me esp for instances like the Resources app.
The dead-ends I tried in order to route to crop-probability were:
For the crop icons:
Screenshots