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
The regex configuration can be complex to use, so there should be an alternative that is simple to use and works for most cases with reasonable defaults.
To do this, a path-based location can be created.
For example, to configure a local resolver, the directory and prefix can be specified using the file scheme:
"file://data/prefix
This would mean that requests to /reads/prefix/<id> would be accepted by this resolver, and look for files in the local directory at data.
Similar concepts can be made for S3 and URL storage:
"s3://bucket/prefix"
"https://example.com/prefix"
The text was updated successfully, but these errors were encountered:
The regex configuration can be complex to use, so there should be an alternative that is simple to use and works for most cases with reasonable defaults.
To do this, a path-based location can be created.
For example, to configure a local resolver, the directory and prefix can be specified using the file scheme:
This would mean that requests to
/reads/prefix/<id>
would be accepted by this resolver, and look for files in the local directory atdata
.Similar concepts can be made for S3 and URL storage:
The text was updated successfully, but these errors were encountered: