The existing type of module works well for simple, numeric data, but is not adequate for long-form information.
Enter the interaction module! The interaction module allows users to access views with long-form data. The only visual difference is that this module's description is followed by an arrow to indicate its purpose.
The best way I found to accomplish having two separate types of modules was to consolidate them into a single directive called gocoModule. The directive accepts a "type" parameter that defines the module's behavior.
When tapped, the interaction module changes state to /moduleview. The endpoint name is passed as a parameter and used to determine what template to load inside the module view.
The existing type of module works well for simple, numeric data, but is not adequate for long-form information.
Enter the interaction module! The interaction module allows users to access views with long-form data. The only visual difference is that this module's description is followed by an arrow to indicate its purpose.
The best way I found to accomplish having two separate types of modules was to consolidate them into a single directive called
gocoModule. The directive accepts a "type" parameter that defines the module's behavior.When tapped, the interaction module changes state to
/moduleview. The endpoint name is passed as a parameter and used to determine what template to load inside the module view.