1. 04 Oct, 2021 1 commit
  2. 27 Sep, 2021 1 commit
    • sam marshall's avatar
      MDL-72643 core: Improve display_size · e332d184
      sam marshall authored
      Allows display_size to use a fixed unit for easy comparison of
      multiple results, and fixed decimal places for the same reason.
      
      Improves behaviour by using consistent decimal places and a
      consistent space before the unit (the previous one only has a space
      before 'bytes', not before 'KB').
      
      Of existing uses, all the ones that displayed a 'maxbytes' type
      configuration setting (which are likely to have an 'exact' size
      and would be better shown as 512 KB rather than 512.0 KB) have been
      changed to use 0 decimal places, to preserve previous behaviour.
      All the uses which were showing an actual file or memory size have
      been left as default (1 decimal place).
      e332d184
  3. 24 Sep, 2021 2 commits
  4. 17 Sep, 2021 1 commit
  5. 13 Sep, 2021 1 commit
  6. 08 Sep, 2021 1 commit
    • Safat Shahin's avatar
      MDL-71614 qbank_previewquestion: Add Preview question plugin to core · 0d55b26d
      Safat Shahin authored
      
      
      This implementation will introduce a qbank plugin "previewquestion"
      which will view the preview question action in the question bank
      actions by replacing the core classes, scripts and yui modules.
      This plugin will also replace the preview option in the edit
      question form. Having this plugin will give users the
      flexibility of enabling or disabling this feature from
      the question bank view.
      This change will also allow other qbank plugins to add
      elements or information in the preview question page
      by implementing a callback. It also changes the pop
      up to page redirect from base view page to make sure
      any changes in preview reflects in the base view, for
      example, comments added and the number of comments in
      the comments colum changes while back from the preview
      page. Other locations like edit and qtype plugins where
      the preview is implemented, stays the same.
      Co-Authored-By: default avatarGuillermo Gomez Arias <guillermogomez@catalyst-au.net>
      Co-Authored-By: default avatarSafat Shahin <safatshahin@catalyst-au.net>
      0d55b26d
  7. 07 Sep, 2021 1 commit
  8. 03 Sep, 2021 1 commit
    • Guillermo Gomez's avatar
      MDL-71585 qbank_managecategories: Add managecategories to core · fb10b36c
      Guillermo Gomez authored
      This implementation will introduce a qbank plugin "managecategories"
      which will add the question categories feature in the question bank view
      by replacing the core classes. Having this plugin will give users
      the flexibility of enabling or disabling the category tab.
      fb10b36c
  9. 31 Aug, 2021 2 commits
  10. 27 Aug, 2021 1 commit
  11. 12 Aug, 2021 1 commit
  12. 10 Aug, 2021 1 commit
  13. 03 Aug, 2021 1 commit
  14. 27 Jul, 2021 1 commit
  15. 13 Jul, 2021 1 commit
  16. 21 Jun, 2021 1 commit
  17. 18 Jun, 2021 1 commit
  18. 02 Jun, 2021 1 commit
  19. 26 May, 2021 7 commits
    • Peter Dias's avatar
      f9913970
    • Andrew Nicols's avatar
      743d17ff
    • Andrew Nicols's avatar
      MDL-70990 core_block: Replace legacy BLOCK_CONTENT_UPDATED event · 31d6adef
      Andrew Nicols authored
      The legacy M.core.event.BLOCK_CONTENT_UPDATED event has been replaced with a
      new core_block/events::blockContentUpdated native DOM event.
      
      The new event can be triggered using the `notifyBlockContentUpdated`
      event, and by providing the HTMLElement that was updated, for example:
      
      ```
      import {notifyBlockContentUpdated} from 'core_block/events';
      
      const someHandler = e => {
          // ...
          const updatedBlock = e.target.closest('.block');
          notifyBlockContentUpdated(updatedBlock);
      };
      ```
      
      The new event can be listened to at any point in the DOM using the
      following syntax:
      
      ```
      import {eventTypes} from 'core_block/events';
      
      const handler = e => {
          // The block that was updated.
          e.target;
      
          // The id of the updated block.
          e.detail.instanceId;
      };
      
      document.addEventListener(eventTypes.blockContentUpdated, handler);
      ```
      
      A backward-compatabibility layer is included to ensure that any legacy
      YUI event listener is still called with the same arguments.
      
      This legacy bridges will be removed after Moodle 4.3.
      31d6adef
    • Andrew Nicols's avatar
      MDL-70990 core_filter: Add new native filterContentUpdated event · d4c6ac20
      Andrew Nicols authored
      The legacy M.core.event.FILTER_CONTENT_UPDATED event has been replaced with a
      new core_filter/events::filterContentUpdated native DOM event.
      
      The new event can be triggered using the `notifyFilterContentUpdated`
      function, and by providing with an Array containing the HTMLElements
      that were updated, for example:
      
      ```
      import {notifyFilterContentUpdated} from 'core_filter/events';
      
      const someHandler = e => {
          // ...
          const nodeList = Array.from(document.querySelectorAll('div'));
          notifyFilterContentUpdated(nodeList);
      };
      ```
      
      The new event can be listened to at any point in the DOM using the
      following syntax:
      
      ```
      import {eventTypes} from 'core_filter/events';
      
      const handler = e => {
          // The list of HTMLElements in an Array.
          e.detail.nodes;
      };
      
      document.addEventListener(eventTypes.filterContentUpdated, handler);
      ```
      
      A backward-compatabibility layer is included to ensure that any legacy
      YUI event listener, or jQuery event listener are still called with the
      same arguments.
      
      This legacy bridges will be removed after Moodle 4.3.
      d4c6ac20
    • Andrew Nicols's avatar
      MDL-70990 core_editor: Replace EDITOR_CONTENT_RESTORED event · a44cee78
      Andrew Nicols authored
      The legacy M.core.event.EDITOR_CONTENT_RESTORED event has been replaced
      with a new core_editor/events::editorContentRestored native DOM event.
      
      The new event can be listened to at any point in the DOM using the
      following syntax:
      
      ```
      import {eventTypes} from 'core_editor/events';
      
      document.addEventListener(eventTypes.editorContentRestored, handler);
      ```
      
      A backward-compatabibility layer is included to ensure that any legacy
      jQuery event is still called with the same arguments.
      
      This legacy bridge will be removed after Moodle 4.3.
      a44cee78
    • Andrew Nicols's avatar
      MDL-70990 core_form: Replace FORM_SUBMIT_AJAX event · acd9d982
      Andrew Nicols authored
      The legacy M.core.event.FORM_SUBMIT_AJAX ecent has been replaced with a
      new core_form/events::formSubmittedByJavascript native DOM event.
      
      The new event can be listened to at any point in the DOM using the
      following syntax:
      
      ```
      import {eventTypes} from 'core_form/events';
      
      document.addEventListener(eventTypes.formSubmittedByJavascript, handler);
      ```
      
      A backward-compatabibility layer is included to ensure that any
      legacy YUI event triggered on a form is still respected and the new
      native event is also fired.
      
      A similar handler is also included to ensure that any legacy YUI event
      listener is still called with the same arguments.
      
      These legacy bridges will be removed after Moodle 4.3.
      acd9d982
    • Andrew Nicols's avatar
      MDL-70990 core: Rewrite core/event as ES6 · da8658e4
      Andrew Nicols authored
      da8658e4
  20. 06 May, 2021 1 commit
    • Eloy Lafuente's avatar
      MDL-71420 environment: Add some strategic comments and todos. · d676a811
      Eloy Lafuente authored
      This isn't really a deprecations where something is replaced
      by another and all uses must adapt to. Instead it's just a
      fallback functionality that will stop working in Moodle 4.2.
      
      Because of that, I've tried to add TODO/@todo comments to
      the places that will need to modified, always pointing to
      MDL-71421 that is where the removal will happen.
      
      Also, haven't added any debugging() output, after thinking
      a lot about it, because this isn't anything that developers
      can be using but a internal implementation detail (a fallback)
      that we want to remove in some versions.
      d676a811
  21. 03 May, 2021 1 commit
  22. 28 Apr, 2021 1 commit
  23. 18 Apr, 2021 1 commit
  24. 14 Apr, 2021 1 commit
    • Xuan Gui's avatar
      MDL-70649 files: Alternative security helper · ed046b8e
      Xuan Gui authored
      Augument all installed plugin's security helper if there is any.
      Plugins function has to be defined as plugintype_pluginname_security_helper in pluginname/lib.php file.
      ed046b8e
  25. 25 Mar, 2021 1 commit
  26. 22 Mar, 2021 1 commit
  27. 17 Mar, 2021 1 commit
  28. 15 Mar, 2021 1 commit
    • Mihail Geshoski's avatar
      MDL-44613 behat: strftime format in time to timestamp transformation · 9fadf911
      Mihail Geshoski authored
      Modifies the 'string time to timestamp' behat trasformation to use
      userdate() instead of date(). The userdate() method is generally used
      throught Moodle for constructing formatted date strings and this change
      will provide more consistency and prevent any potential behat failures.
      Therefore, if the date format is defined in the given trasformation, it
      has to be strftime compatible. Example:
      'I should see "##tomorrow noon##%A, %d %B %Y, %I:%M %p##"'
      9fadf911
  29. 12 Mar, 2021 1 commit
  30. 09 Mar, 2021 1 commit
  31. 08 Mar, 2021 2 commits