-
Notifications
You must be signed in to change notification settings - Fork 114
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
[DP] Rename datapackage.json to package.json in Data Package #73
Comments
I'm still a bit mixed in my feelings here. Changing datapackage.json to package.json is a pretty major change in the spec. The major reasoning is the ability to reuse npm directly but I'm not totally sure yet how much we will directly reuse npm (e.g. we may reuse parts but probably with a bit of modding ...) Pros to package.json:
Cons:
@sballesteros @paulfitz love your thoughts here ... |
WONTFIX. We have agreed to keep datapackage.json, reasoning being:
|
* Rework 'READ MORE' links (i.1) * Add missing alt to images (i.4) * Updated dependencies * Fixed colors using WCAG Contrast checker (i.5) * Fixed foreign key links (of.1) * Fixed linting * Fixed build
Reasoning: we already follow CommonJS package spec very closely and this would allow us to leverage the npm (node package manager) ecosystem directly (a big win!)
See for further discussion this thread: openknowledge-archive/datapackage.js-deprecated#3
The text was updated successfully, but these errors were encountered: