Uploaded image for project: 'PUBLIC - Liferay Portal Community Edition'
  1. PUBLIC - Liferay Portal Community Edition
  2. LPS-113562

Modernize or deprecate frontend-js-aui-web's liferay/deprecated.js

    Details

    • Type: Task
    • Status: Closed
    • Priority: Minor
    • Resolution: Completed
    • Affects Version/s: None
    • Fix Version/s: Master
    • Component/s: Alloy UI
    • Labels:
      None

      Description

      In service of this epic:

      https://issues.liferay.com/browse/LPS-112938 ("AUI modernization, the sequel")

      Which is itself part of the larger project:

      https://issues.liferay.com/browse/LPS-98564 ("Remove AUI / YUI from Liferay Portal")

      Our end goal is to remove all dependency on AUI/YUI from liferay-portal. We will have succeeded when we get to the point that we can turn off the frontend-js-aui-web module default, and nothing in liferay-portal breaks.

      For this task, we have to analyze this file:

      https://github.com/liferay/liferay-portal/blob/master/modules/apps/frontend-js/frontend-js-aui-web/src/main/resources/META-INF/resources/liferay/deprecated.js

      And once we understand what it does and how it is used, decide whether to:

      1. Mark it as deprecated (because it is no longer used); or:
      2. Modernize the JS and port it to another location (eg. frontend-end-js-web if it is reusable and useful, or embedding it locally somewhere else if it is less of a general utility) so that we no longer depend on frontend-js-aui-web for this functionality.
      3. Actually perform the changes.

      Note that we want to do this in a non-breaking way: all the functionality in liferay-portal should keep working, and any customer relying on this AUI-based functionality should be able to continue using it, provided they keep the frontend-js-aui-web module activated.

      Also note that we have lots of tickets related to AUI removal, organized into several epics, so a good first step before starting work is to do a search of Jira to double-check that this isn't already covered by some other ticket. At least at the time of writing, our current understanding of the state of the migration is in this spreadsheet:

      https://docs.google.com/spreadsheets/d/1Z3JKIM0Z3rohRHXTQ3YcLzeVKcTYaUl9TxOpFb8PCb0/edit#gid=0

        Attachments

          Activity

            People

            Assignee:
            jose.balsas Chema Balsas (Inactive)
            Reporter:
            greg.hurrell Greg Hurrell (Inactive)
            Engineering Assignee:
            Julien Castelain
            Recent user:
            Tomáš Polešovský
            Participants of an Issue:
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Packages

                Version Package
                Master