Take into account basepath for describe
See original GitHub issueOverview
As a user, I want to create a data package from my root project directory and then save it e.g. to a data directory. Currently, providing a basepath to describe
doesn’t change the paths inside the package (still from the root).
frictionless describe --basepath data 'data/*.csv' > data/package.json
# will create a package with paths relative to a root dir
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Basepath Definition & Meaning - Merriam-Webster
The meaning of BASEPATH is the area between the bases of a baseball field used by a base runner.
Read more >API Host and Base Path - Swagger
REST APIs have a base URL to which the endpoint paths are appended. The base URL is defined by schemes , host and...
Read more >How should basePaths for multiple environments be specified?
It has been split to 3 properties - scheme , host and basePath . The basePath now becomes the actual base path which...
Read more >BasePaths attribute in main xml file - Google Cloud Community
Solved: There is a BasePaths attribute that is in the highest level XML file for a proxy. It looks like this field doesn't...
Read more >AWS::ApiGateway::BasePathMapping - AWS CloudFormation
The base path name that callers of the API must provide in the URL after the domain name. Required: No. Type: String. Update...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hey again, I’m on it 😃
Hey @roll,
I found the bug under program/desribe.py.
I have created a PR - #875