You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@matt8707 curious what your thoughts are, or how you thought about handling the components that are only available to sidebar. Do you think SidebarItemConfig and MainItemConfig should be refactored into 1?
If separate, how would you imagine handling the content rendering?
I've created a PR (on my local) just to see what all it would take (this is keeping both Main and Sidebar config). I've only implemented "Bar" from sidebar but all objects are available and editable. But determining the best way to display the content as they are implemented differently.
Also this is my first svelte project, so just a few hours in. open for any suggestions.
*also, with this test you can't actually edit the component once its created likely due to the differences in sidebar/main implements.
The text was updated successfully, but these errors were encountered:
Yeah, there will be small (or large) differences in how the component looks and behaves depending on whether it's in the sidebar or main section. To stay sane while prototyping, they're split up for now. However, the plan is to merge them further down the line.
@matt8707 curious what your thoughts are, or how you thought about handling the components that are only available to sidebar. Do you think SidebarItemConfig and MainItemConfig should be refactored into 1?
If separate, how would you imagine handling the content rendering?
I've created a PR (on my local) just to see what all it would take (this is keeping both Main and Sidebar config). I've only implemented "Bar" from sidebar but all objects are available and editable. But determining the best way to display the content as they are implemented differently.
Also this is my first svelte project, so just a few hours in. open for any suggestions.
*also, with this test you can't actually edit the component once its created likely due to the differences in sidebar/main implements.
The text was updated successfully, but these errors were encountered: