-
-
Notifications
You must be signed in to change notification settings - Fork 246
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
Entity API #14
Milestone
Comments
lalalune
created this issue from a note
in XRChat Sprint 1 Feature List
(To Do: Backend Server)
Apr 8, 2020
Before we dive into this, let's make sure we're on the same page with Webaverse, etc. We want to package media and references to media where possible. |
dmitrizagidulin
assigned barankyle and mohrtw and unassigned dmitrizagidulin and lalalune
Apr 8, 2020
dmitrizagidulin
removed this from To Do: Backend Server
in XRChat Sprint 1 Feature List
Apr 15, 2020
lalalune
modified the milestones:
XRChat Full Deployment Sprint 1,
Due Date: May 4th, 2020
Apr 19, 2020
@dmitrizagidulin closing this since entities have been added. |
lalalune
added a commit
that referenced
this issue
Nov 23, 2020
patreeceeo
pushed a commit
to MappaLabs/MappaXRE
that referenced
this issue
Dec 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What does this feature do?
We want to be able to consume objects and store them, and then make them available when requested.
Actual objects and resources will be uploaded to S3 via our storage API. @barankyle has done this.
First step: Add CRUD for objects. Owner is 'server' (default) unless it is attached to a userID
We already have an Objects API. Update the objects.model.ts to have a list of resources
Feathers automatically makes CRUD -- read documentation to override if necessary
class Object(){
id: number (unique)
owner: relation to user (empty for server)
created: dateTime
modified: dateTime
resource: {type, url}
}
Second step: Integrate with Storage API
AddResourceToObject ({objectId, type, url}) -- Upload new resource and attach it to the object
Third Step: Component on front end that lets user upload a GLTF or GLB (POST)
Fourth step Add image upload, OBJ and FBX upload (POST)
Fifth Step Form shows object, user can edit or replace resource (UPDATE) to delete (DELETE)
Sixth step: Integration with XRPackage. Upload and download XRPackages
Please check out:
https://github.com/webaverse/xrpackage
The text was updated successfully, but these errors were encountered: