feat: introduce components db #841
Open
+522
−279
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
n1k0
force-pushed
the
chore/components-datasource
branch
from
7a50599
to
646c900
Compare
n1k0
force-pushed
the
chore/components-datasource
branch
from
646c900
to
98302ee
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🔧 Problem
We don't have a components database and explorer for objects and veli just yet. Also, a component db and handling api would establish good foundations for further work with textile trims (though this patch doesn't make components totally generic just yet, but that'd be the next step).
🍰 Solution
Introduce a components JSON database with reusable default components for objects and veli. Add a component explorer as well.
🏝️ How to test
Ensure the explorer works well and that the objects and veli simulators still work as expected.