You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ilya Borisov (Jira)" <ji...@apache.org> on 2019/08/30 06:32:00 UTC

[jira] [Resolved] (IGNITE-9476) Web console: extract configuration-specific mixins from mixins.pug

     [ https://issues.apache.org/jira/browse/IGNITE-9476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ilya Borisov resolved IGNITE-9476.
----------------------------------
    Resolution: Duplicate

Already done in https://issues.apache.org/jira/browse/IGNITE-9879.

> Web console: extract configuration-specific mixins from mixins.pug
> ------------------------------------------------------------------
>
>                 Key: IGNITE-9476
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9476
>             Project: Ignite
>          Issue Type: Improvement
>          Components: wizards
>            Reporter: Ilya Borisov
>            Assignee: Alexander Kalinin
>            Priority: Minor
>
> Most of form field Pug mixins used in configuration are very specific to it and are not used elsewhere. The _mixins.pug_ that these currently reside in is too big for my liking. I suggest to move all configuration mixins to configuration module (for example, _page-configure/mixins.pug_), with the following benefits:
>  # All code specific to configuration will stay in configuration module.
>  # mixins.pug will become easier to maintain.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)