Skip to content
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

Async API sidebar TypeError during navigation #2532

Open
alucarddelta opened this issue May 9, 2024 · 2 comments
Open

Async API sidebar TypeError during navigation #2532

alucarddelta opened this issue May 9, 2024 · 2 comments

Comments

@alucarddelta
Copy link

alucarddelta commented May 9, 2024

When viewing a AsyncAPI document, clicking on any of the side bar objects does not change the main panel. The options have the hover effect, but when selected nothing occurs.

This also occurs when creating a new Channel, Data Type, ect. When creating after hitting save when creating a "name" of the object, when the page refreshes, the main panel does not update to allow the input of options. The side bar also does not update with the newly entered object. However when you save (blue top right button) and refresh the page, the side bar updates, but again selecting the option does not update the main panel.

An error appears in the console when any of the side bar options is selected.

ERROR TypeError: Cannot read properties of null (reading 'accept')

This occurs with when creating a blank document, using the streetlights demo file, or importing an external document.

image
image

@JeSuisAlrick
Copy link

Hey guys,

This solution is unusable in its current state. We appreciate the work and understand that this is an opensource project, but this beta release needed more testing.

CC: @EricWittmann, @alucarddelta, @wtrocki, @jsenko, @paoloantinori

@EricWittmann
Copy link
Member

Thanks for the feedback and apologies for the delay. I missed the original notification.

We definitely focused on open API so that's not great - I'll have a look at fixing the asyncapi Editor as soon as I can.

It's not an excuse but that editor was originally community contributed. So it doesn't get the same level of care and attention a lot of the time.

We'll see what we can do about that as soon as we can.

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

No branches or pull requests

3 participants