Jeong Min Cho

@i-am-chitti It is still a pending issue indeed as I checked. @martmull This issue can be done easily, but there are some catch-ups. ## Problem There were some [lifecycle bugs](https://github.com/graphql/graphiql/commit/bed5fc86173eb0e770f966fa529ee035b97a1349)...

> Hey @Jeong-Min-Cho thank you for your very clear explanation. Do you see any breaking changes in the playground when updating graphiql to version 3.0.10? Hello, thanks for coming back...

@martmull Of course, the pull request is up as you asked! 👍

@charlesBochet Gladly. I also don't want any regression from my pull request either. 😊

@charlesBochet Hello again! The changes are up now 🚀

@Bonapara The pull request for this issue is up now

 I have encountered the same issue on WSL (Ubuntu 20.04.5 LTS), but **not** on Docker. It was the **local setup**. From me, it was fixed by resetting the workspace...

  This seems to be already **fixed** in the main branch. I guess the live version uses the outdated documents.

Hello, I dug up the problem a little. This is actually a regression from #3147 https://github.com/twentyhq/twenty/pull/3147/files#diff-1eb42b8c2309ef48fdce276caaf462df213a70c044ed4b5d48bc27c8cd965656R55  _(I intentionally increased the alpha of the border shadow to view...

Hello, I have a quick question on it. As you said, "The button should take the full width as a regular menu item", should we keep the text on the...