Uh oh!
There was an error while loading. Please reload this page.
Fix sidebar full state - #456
Conversation
Test summaryRun details
View run in Cypress Dashboard ➡️ This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard |
ChristophWurst
commented
Apr 7, 2020
Is this related to what @ma12-co and you did last Friday? |
skjnldsv
commented
Apr 7, 2020
Not at all, this is how we use to do before the sidebar revamp of 18. |
ChristophWurst
commented
Apr 7, 2020
Okay, so what do we need to fix here then? |
skjnldsv
commented
Apr 7, 2020
well, ideally a better way that manually applying some css to the sidebar and overriding style. Does it make sense to have a way to call the sidebar (in server) in full state? Even if maybe only this app uses it? |
ChristophWurst
commented
Apr 7, 2020
What does that mean? Could you link or describe the problem you're trying to solve please? :) |
skjnldsv
commented
Apr 7, 2020
Sure! |
ChristophWurst
commented
Apr 7, 2020
Okay, then I would still say the css approach is okay-ish, right? |
skjnldsv
commented
Apr 7, 2020
Not really. I really don't like overriding styles. |
ChristophWurst
commented
Apr 7, 2020
Then I guess it's complicated. Because the sidebar is not a component rendered by this app. Otherwise we could just pass in the full screen info as boolean flag. We might also have to send this info via an event. The question is just if there is someone who listens as that depends on the order the script are loaded. |
skjnldsv
commented
Apr 15, 2020
/compile amend / |
skjnldsv
commented
Apr 15, 2020
/backport to stable18 |
Signed-off-by: npmbuildbot[bot] <npmbuildbot[bot]@users.noreply.github.com>
f547a38 to
c840783Comparebackport to stable18 in #470 with conflicts |
Fix full state Of sidebar
So, I really dislike this. @ChristophWurst@juliushaertl how would you do this? Let the Sidebar in files listen to an event? 🤷♀️