•  
      request #42982 Fixable Sass deprecations
    Infos
    #42982
    Joris MASSON (jmasson)
    2025-06-04 11:46
    2025-05-12 17:39
    44664
    Details
    Fixable Sass deprecations

    The build tasks of Tuleap frontend apps report several Sass deprecations. Those will not cause problems yet, but it could stop us from doing a future upgrade of Sass. We should fix them.

    Impacted components:

    • [x] core-project-registration
    • [x] plugin-projectmilestones
    • [x] core / FlamingParrot styles: @import, slash division
    • [x] core / BurningParrot styles: @import, global functions, slash divisions
    • [x] plugin agiledashboard FlamingParrot styles: @import
    • [x] plugin baseline styles: @import
    • [x] plugin document styles: @import
    • [x] plugin FRS styles: @import
    • [x] plugin LDAP styles: @import
    • [x] plugin statistics styles: @import

    Note that some Sass deprecations are "not our fault"™️, for example the current version of FontAwesome still uses @import which is deprecated, so until they fix and ship the fixed version, we will keep seeing them.
    Public issue for FontAwesome: https://github.com/FortAwesome/Font-Awesome/issues/19167

    Impacted components for "not our fault":

    • print-as-pdf: "print-js" dependency uses @import
    • core / FlamingParrot styles: FontAwesome @import, global function
    • project-sidebar-internal: FontAwesome
    • tuleap-documentation-en: FontAwesome
    Dev tools
    Empty
    Empty
    • [ ] enhancement
    • [x] internal improvement
    Empty
    Stage
    Joris MASSON (jmasson)
    Closed
    2025-06-04
    Attachments
    Empty
    References

    Follow-ups

    User avatar
    Joris MASSON (jmasson)2025-06-04 11:46
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Joris MASSON (jmasson)2025-06-03 17:17
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Joris MASSON (jmasson)2025-05-23 12:49
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Joris MASSON (jmasson)2025-05-23 10:31
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Joris MASSON (jmasson)2025-05-23 09:54
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Joris MASSON (jmasson)2025-05-23 09:07

    I shouldn't have closed it, there are still imports in the plugins


    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    • Status changed from Closed to Reopen
    • Close date cleared
    User avatar
    Joris MASSON (jmasson)2025-05-15 18:01
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Joris MASSON (jmasson)2025-05-13 18:16
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Joris MASSON (jmasson)2025-05-13 17:15
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Joris MASSON (jmasson)2025-05-13 16:04
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Joris MASSON (jmasson)2025-05-13 15:49
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Joris MASSON (jmasson)2025-05-13 15:19
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    User avatar
    Joris MASSON (jmasson)2025-05-12 17:57
    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes