• Icon: Sub-task Sub-task
    • Resolution: Fixed
    • Icon: Minor Minor
    • 2.0
    • 2.0
    • Ionic
    • MOODLE_20_STABLE
    • MOODLE_20_STABLE

      We should define how to namespace, and organise the different states of the app. For instance, here are some affirmations and questions:

      • We should never ever state.go() or href= with a URL, always use ui-sref or state.href when relevant
      • Outside a side, and in-site should be in a different level? (prototype uses site/ for everything within a site)
      • How to name the tablet views?
      • How to identify the course that the user is viewing. The prototype uses ?courseId for the participants page. I was thinking that maybe we could try not to pass that parameter ever, but record in the session what course you are viewing. That prevents having to pass the courseId all the way. Though I'm not sure which one is less annoying to debug. Food for thoughts.

      Please add more if you think of any.

            Unassigned Unassigned
            fred Frédéric Massart
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.