-
-
Notifications
You must be signed in to change notification settings - Fork 98
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
add architecture considerations document #739
base: master
Are you sure you want to change the base?
Conversation
|
✅ Deploy Preview for modest-rosalind-098b67 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for asyncapi-studio-design-system ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@fmvilas The problems faced using the current services may also be mentioned.
This works well currently; even things such as navigation in the editor, template and visualiser are working correctly. |
Kudos, SonarCloud Quality Gate passed! |
@Shurtu-gal I wonder if that's something related to the current architecture. Maybe, with the new architecture, we can find a way to make this easier? I mean, with a couple of exceptions, everything should be executable on the server and on the client. What do you think? |
Yeah, if we separate it instead of maintaining it on the client. These problems will be solved by themselves. This way, the object of concern may be separated, and services may be exposed as APIs. P.S.:- But things like navigation and theme setting would have to be handled on the client side using context and hooks. |
@fmvilas @Shurtu-gal I think it's a valid question that we should cover under the new architecture ? When do we use Hooks ? and also How to share state between components ? do we use React Context or Zustand |
Agree. We'll have to address all these questions. Who wants to take the lead here? |
This pull request has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation. There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
Still relevant |
Quality Gate passedIssues Measures |
This pull request has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 120 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation. There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
Description
Some initial considerations for the new Studio architecture.
Related issue(s)
#725