Skip to content
This repository has been archived by the owner on May 22, 2023. It is now read-only.
This repository has been archived by the owner on May 22, 2023. It is now read-only.

Fix initial event (broken didChangeLocale/Theme) #48

Closed
x1B opened this issue Mar 3, 2017 · 2 comments
Closed

Fix initial event (broken didChangeLocale/Theme) #48

x1B opened this issue Mar 3, 2017 · 2 comments

Comments

@x1B
Copy link
Member

x1B commented Mar 3, 2017

Probably due to some copy/paste error, didChangeLocale is published twice initially, the second time with a theme payload. Should be didChangeTheme.

@x1B x1B added this to the v2.0.0 milestone Mar 3, 2017
@x1B x1B self-assigned this Mar 3, 2017
@x1B x1B changed the title Fix Fix initial event (didChangeLocale -> didChangeTheme) Mar 3, 2017
@x1B
Copy link
Member Author

x1B commented Mar 3, 2017

Revisiting: we already dropped didChangeTheme from the runtime, so let's just get rid of it.

@x1B x1B changed the title Fix initial event (didChangeLocale -> didChangeTheme) Fix initial event (broken didChangeLocale/Theme) Mar 3, 2017
@x1B x1B added breaking and removed type: bug labels Mar 3, 2017
x1B added a commit that referenced this issue Mar 3, 2017
@x1B
Copy link
Member Author

x1B commented Mar 3, 2017

Implemented on master (v2.0.0).

BREAKING CHANGE

In accordance with LaxarJS core, no didChangeTheme event is published anymore when using triggerStartupEvents.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants