Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-76430

Course editor: replace activity and section refresh webservices for fragment methods

XMLWordPrintable

    • 2
    • HQ Sprint 1.3 Moppies

      Since Moodle 4.0 the course editor frontend part uses two main modules to handle the edition tools:

      • core_course/actions: responsible for handling all non-reactive tools and the legacy formats
      • core_courseformat/courseeditor: the new reactive library that updates the course index and the course content

      Since the reactive implementation starts, the final goal is to replace all legacy actions with new ones as soon as possible. The most complex ones like moving elements, deleting, and creating sections are already migrated and others like indent are just deprecated (or leave it to third-party plugins).

      One of the major dependencies of the new reactive library is that it still rely on the old actions to refresh an activity or a section. This issue will implement proper fragment methods to get both activity and section HTML and JS without using the old YUI methods.

      There's a proof of concept of the highlight option migrated entirely to the topics format:

      https://github.com/ferranrecio/moodle/commit/9576978d6d825d6c1ef0d695cc9eef6f0173fea3

       

            tusefomal Ferran Recio
            tusefomal Ferran Recio
            Carlos Escobedo Carlos Escobedo
            Jun Pataleta Jun Pataleta
            CiBoT CiBoT
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - 0 minutes
                0m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 2 days, 10 minutes
                2d 10m

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