-
Notifications
You must be signed in to change notification settings - Fork 3
Open
Description
The xr tool should have a transform option that can do a couple of tricks, most of which the code base should already be able to do:
Given a --model:
Sources:
- running xreg server
- import a complete directory structure of staged input files whereby the directories must correspond to the registry structure. If the model resource is hasdocument:true, import the files as docs and infer metadata as good as possible. If false, validate JSON files against the model structure.
- import a full export file or one just with top level groups
- import a single xRegistry export or file with top level groups
Target:
- static site (output of "xr download")
- document directory (same as static site but w/o the xr json files)
- single file with embedded docs (same as "GET /export")
- single file with pointers to source docs (same as "GET /export" BUT no inlining of RESOURCE, point to files on disk)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels