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
[UI] Designer Configurator should use Meshmodel component. #7356
Comments
This issue has been labeled with 'component/ui'. 🧰 Here are docs on Contributing to Meshery UI. 🎨 Here is the Meshery UI Figma File File. Lastly, here are docs on Contributing to Meshery's End-to-End Tests Using Cypress.
|
Get list of All Models: Get components from a certain Model: Get certain component from certain model All the rest API endpoints are available here Its better suited to start from scratch then making the changes in the current functional components. The new component should suit well, because a lot of things has been changed that is not incorporated in the current UI. |
LGTM, i can work on this issue @Abhishek-kumar09 @harkiratsm |
Thanks for taking this issue, @yash37158 Let me know if you need any help here. You can always be vocal about it in slack or github issue thread. |
Yeah sure |
Hey @Abhishek-kumar09 do we have a separate folder for design patterns? where can I see the code for k8s? |
The data is loaded dynamically, and the the layout and its state management is being done in React. Here are some files involved:
IMO, the point 2 will be the area where you can refer some things and it mostly requires a complete re-write. |
I am unassigning myself from this issue, if this issue still persists would try to take up that in future @leecalcote @Abhishek-kumar09 |
@harkiratsm if no one else gets assigned today, then please self-assign this issue. |
I am taking this on. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
completed #7578 |
Current Behavior
Currently, the designer configurator is using oam interface.
Desired Behavior
Since we had moved forward with meshmodel, we need all the categories and components in place for that in the design configurator itself.
Implementation
Under the Meshery API endpoints doc, you can find meshmodel endpoints.
Visit the meshmap playground to find out what you're working on.
Contributor Guides and Handbook
The text was updated successfully, but these errors were encountered: