samz
samz
Do we want to wait until the next architecture https://github.com/asyncapi/studio/issues/725 is completed before integrating the components ? Any thoughts ? @Shurtu-gal @fmvilas @KhudaDad414
@divyammadhok you might be interested to joining this effort: https://asyncapi.slack.com/archives/CQVJXFNQL/p1690810559915289
We don't need to add the avatar as we don't support users (signin/signup) in studio @utnim2
Best to coordinate with @Shurtu-gal as he is working on the NextJS migration, I suggest to add this enhancement as part of the new app in `apps/studio-next`
@utnim2 @Shurtu-gal is adding the Editor to NextJS app in this PR https://github.com/asyncapi/studio/pull/997 (still under review), this will be useful here.
@KhudaDad414 I guess migrating to NextJS will help us find a workaround on the server side.
@KhudaDad414 If we find a way to always have the latest working version running locally, would that solve the issue? I'm not sure about the security/internet requirement trade-off. I also...
Thanks @RobinTail for reporting this issue, this is related to our asyncapi-react dependency that we use to render documentation, I have reported the issue here: https://github.com/asyncapi/asyncapi-react/issues/993
still relevant
@KristinaB162 The highest severity issues are present in the dependencies we don't have control over: `@oclif/plugin-commands` and `@oclif/plugin-warn-if-update-available` Created https://github.com/oclif/plugin-commands/issues/661