ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Kuznetsov (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-6833) Web Console: runtime errors after each SCSS save
Date Fri, 10 Nov 2017 03:46:00 GMT

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

Alexey Kuznetsov reassigned IGNITE-6833:
----------------------------------------

    Resolution: Fixed
      Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Merged to master. Please retest.

> Web Console: runtime errors after each SCSS save
> ------------------------------------------------
>
>                 Key: IGNITE-6833
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6833
>             Project: Ignite
>          Issue Type: Bug
>      Security Level: Public(Viewable by anyone) 
>          Components: wizards
>         Environment: Windows 10, MacOS, master branch
>            Reporter: Ilya Borisov
>            Assignee: Pavel Konstantinov
>             Fix For: 2.4
>
>         Attachments: screenshot-1.png
>
>
> *What happens:*
> Web console frontend throws runtime errors after every SCSS file save. You have to save
any non-stylesheet file to fix the error.
> *How to reproduce:*
> 1. Checkout master.
> 2. Start frontend development environment.
> 3. Save any SCSS file, no changes necessary.
> 4. Open local web console, open browser console, see the error.
> *Expected behavior:*
> No errors should happen after SCSS file saves.
> *Note:*
> I had a hand at this earlier: the error always mentions missing global dependency of
some sort (i.e. _.head). If you replace all implicit lodash uses with explicit imports in
every file, error eventually starts to point at polyfills (i.e. RegExp.esacpe). Maybe this
will be of help, I did not progress any further.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message