New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Angular update #7147
Angular update #7147
Conversation
ng-bind-html-unsafe was apparently removed.
This used to use "success", which was our own thing, but which I can't get working. So instead we just use ".then", which only passes one object as an argument that then contains all the other data we use. This should be enough to complete the port to angular 1.8
Clicking the Dracula theme gives this error and breaks the "Customize" button.
That's the only regression I see from a cursory look through all the tabs. |
That could actually be a bug in the colorscheme? I'm not sure what that "colors" array is good for. Also is it possible that some of the colorschemes are either broken themselves or have a wrong background color? For "Snow Day" and "Tomorrow" the suggestions aren't visible to me (but my color vision is impaired, so I'm never quite sure). |
Look ok here, though also note #7117 |
Dracula theme has always had a duplicate color (#3723).
These are the selectable colors that show up when you press "Customize". It's fine to have 11 colors in the array, as evidenced by other themes in colorutils.js. I believe the fix is to remove the duplicate. Also came across an official Dracula fish theme: It differs from the settings we have. But that's for a different PR. |
This seems to work OK for me too with light testing. |
This was always wrong, but the new(er) angular actually complains about it.
Yeah, merged with the Dracula fix, let's see if it shakes anything else out. |
Description
As recently discussed on gitter, webconfig uses angular 1.0.8, from 2013.
This ports it to angular 1.8, which entered a 3 year LTS period in 2018. Hey, that's almost new.
As far as I can tell that means angular is dead, so we'd have to figure out something to move to.
So this is more of a stop gap.
(also webconfig is in dire need of some love anyway)
TODOs:
Note that I have only applied light testing - I clicked through all the tabs and they seemed to work for me.