Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #11367 BurningParrot and FlamingParrot SCSS files should not be mixed
    Actions
    Infos
    #11367
    Joris MASSON (jmasson)
    2018-04-06 18:11
    2018-04-06 13:34
    11685
    Details
    BurningParrot and FlamingParrot SCSS files should not be mixed
    It's already hard enough to figure out which files go where without having to look in build-manifest.json if BurningParrot builds a file from FlamingParrot.
    One day, we will want to remove FlamingParrot and this will blow up in our faces then.
    So, instead we should @import a common file and have two separate "entrypoints".
    Agile Dashboard
    9.19
    Empty
    • [ ] enhancement
    • [x] internal improvement
    Empty
    Stage
    Empty
    Closed
    2018-04-06
    Attachments
    Artifact links

    Releases

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #10995 Tuleap Releases 10.0 Delivered 2018-26-04 12:21 Manuel Vacelet (vaceletm)
    Empty
    References
    Referencing request #11367

    Git commit

    tuleap/tuleap/stable

    Merge 'gerrit #10994' into stable/master 24f9d725b3
    User avatar Thomas Gerbet (tgerbet) , 2018-04-06 18:11
    request #11367 BurningParrot and FlamingParrot SCSS files should not be mixed 823d5d1371
    User avatar Joris MASSON (jmasson) , 2018-04-06 13:40
    Referenced by request #11367

    Artifact Tracker v5

    rel #10995 10.0

    Other

    gerrit #10994
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2018-04-06 18:11
    Thanks!


    Integrated into Tuleap 9.19.99.44.
    • Status changed from Under review to Closed
    • Connected artifacts
    • Close date set to 2018-04-06