specs
specs copied to clipboard
frictionlessdata
Mention v2 in v1 specs?
What Data Package version are you using?
v2
Describe the Issue
Since v1 specs still appear near the top of search results and probably will for some time, perhaps we could add a small notification box at the top of the v1 specs letting people know that there is a more recent version?
It doesn't have to be a bright red "error" style box like one might see in the legacy react docs, but some form of heads up?
Participation
- [ ] I am willing to submit a pull request for this issue.
That would be great @khughitt. Something a bit like what we did for the old v4 documentation of the Python Framework (maybe even more visible) could be good: https://v4.framework.frictionlessdata.io/docs/guides/guides-overview
Just wanted to give a +1 to this — I landed on the v1 docs via ChatGPT and didn't realize there was a v2! It might help newcomers to have that banner 😊
Thank you for this awesome project, looking forward to checking out v2.
Thanks for flagging this @bertday.
@khughitt, if you are still up for creating a PR to put up that banner, please go ahead!
Hi @sapetti9, I made the changes - https://github.com/frictionlessdata/datapackage/commit/16ef8f781ccc0a099ae7a268591f45fe77e87e78 - but it doesn't deploy. I think v1 it's configured to use Cloudflare but I don't have access to the admin panel to see the error
I took a look at the logs.
I'm wondering if it would be nice to move this deployments and hostings to Github Actions/Github Pages so it is accessible to all the maintainers. Any preference @roll ?
12:05:11.954 Cloning repository...
12:05:12.614 From https://github.com/frictionlessdata/datapackage
12:05:12.614 * branch 16ef8f781ccc0a099ae7a268591f45fe77e87e78 -> FETCH_HEAD
12:05:12.615
12:05:12.646 HEAD is now at 16ef8f7 Aded v2 link to the navbar
12:05:12.647
12:05:12.721
12:05:12.721 Using v2 root directory strategy
12:05:12.741 Success: Finished cloning repository files
12:05:14.385 Checking for configuration in a Wrangler configuration file (BETA)
12:05:14.386
12:05:15.494 No wrangler.toml file found. Continuing.
12:05:16.577 Preparing [email protected] for immediate activation...
12:05:16.863 Preparing [email protected] for immediate activation...
12:05:17.094 Detected the following tools from environment: [email protected], [email protected]
12:05:17.094 Installing project dependencies: yarn
12:05:17.631 ➤ YN0070: Migrating from Yarn 1; automatically enabling the compatibility node-modules linker 👍
12:05:17.631
12:05:17.732 ➤ YN0000: ┌ Resolution step
12:05:18.109 ➤ YN0061: │ glob@npm:7.1.2 is deprecated: Glob versions prior to v9 are no longer supported
12:05:18.159 ➤ YN0061: │ json-schema-ref-parser@npm:9.0.9 is deprecated: Please switch to @apidevtools/json-schema-ref-parser
12:05:18.162 ➤ YN0061: │ inflight@npm:1.0.6 is deprecated: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
12:05:19.184 ➤ YN0061: │ glob@npm:7.2.0 is deprecated: Glob versions prior to v9 are no longer supported
12:05:19.340 ➤ YN0061: │ mkdirp@npm:0.5.1 is deprecated: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
12:05:19.349 ➤ YN0061: │ docsearch.js@npm:2.6.3 is deprecated: This package has been deprecated and is no longer maintained. Please use @docsearch/js.
12:05:19.424 ➤ YN0061: │ webpack-chain@npm:6.5.1 is deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
12:05:19.520 ➤ YN0061: │ glob@npm:7.1.6 is deprecated: Glob versions prior to v9 are no longer supported
12:05:19.665 ➤ YN0061: │ mkdirp@npm:0.3.0 is deprecated: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
12:05:19.717 ➤ YN0061: │ core-js@npm:3.11.2 is deprecated: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
12:05:19.905 ➤ YN0032: │ fsevents@npm:2.3.2: Implicit dependencies on node-gyp are discouraged
12:05:19.905 ➤ YN0061: │ fsevents@npm:1.2.13 is deprecated: Upgrade to fsevents v2 to mitigate potential security issues
12:05:19.942 ➤ YN0061: │ request@npm:2.88.2 is deprecated: request has been deprecated, see https://github.com/request/request/issues/3142
12:05:20.017 ➤ YN0061: │ node-domexception@npm:1.0.0 is deprecated: Use your platform's native DOMException instead
12:05:20.047 ➤ YN0061: │ lodash.template@npm:4.5.0 is deprecated: This package is deprecated. Use https://socket.dev/npm/package/eta instead.
12:05:20.393 ➤ YN0061: │ webpack-chain@npm:4.12.1 is deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
12:05:20.468 ➤ YN0061: │ uuid@npm:3.4.0 is deprecated: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
12:05:20.563 ➤ YN0061: │ @babel/plugin-proposal-class-properties@npm:7.13.0 is deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
12:05:20.622 ➤ YN0061: │ har-validator@npm:5.1.5 is deprecated: this library is no longer supported
12:05:20.668 ➤ YN0032: │ nan@npm:2.17.0: Implicit dependencies on node-gyp are discouraged
12:05:20.802 ➤ YN0061: │ move-concurrently@npm:1.0.1 is deprecated: This package is no longer supported.
12:05:20.875 ➤ YN0061: │ figgy-pudding@npm:3.5.2 is deprecated: This module is no longer supported.
12:05:21.055 ➤ YN0061: │ rimraf@npm:2.7.1 is deprecated: Rimraf versions prior to v4 are no longer supported
12:05:21.093 ➤ YN0061: │ source-map-resolve@npm:0.5.3 is deprecated: See https://github.com/lydell/source-map-resolve#deprecated
12:05:21.152 ➤ YN0061: │ vue@npm:2.6.12 is deprecated: Vue 2 has reached EOL and is no longer actively maintained. See https://v2.vuejs.org/eol/ for more details.
12:05:21.165 ➤ YN0061: │ urix@npm:0.1.0 is deprecated: Please see https://github.com/lydell/urix#deprecated
12:05:21.411 ➤ YN0061: │ querystring@npm:0.2.0 is deprecated: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
12:05:21.469 ➤ YN0061: │ fs-write-stream-atomic@npm:1.0.10 is deprecated: This package is no longer supported.
12:05:21.537 ➤ YN0061: │ copy-concurrently@npm:1.0.5 is deprecated: This package is no longer supported.
12:05:21.733 ➤ YN0061: │ source-map-url@npm:0.4.1 is deprecated: See https://github.com/lydell/source-map-url#deprecated
12:05:21.734 ➤ YN0061: │ resolve-url@npm:0.2.1 is deprecated: https://github.com/lydell/resolve-url#deprecated
12:05:22.011 ➤ YN0061: │ consolidate@npm:0.15.1 is deprecated: Please upgrade to consolidate v1.0.0+ as it has been modernized with several long-awaited fixes implemented. Maintenance is supported by Forward Email at https://forwardemail.net ; follow/watch https://github.com/ladjs/consolidate for updates and release changelog
12:05:22.085 ➤ YN0061: │ @babel/plugin-proposal-dynamic-import@npm:7.13.8 is deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-dynamic-import instead.
12:05:22.093 ➤ YN0061: │ svgo@npm:1.3.2 is deprecated: This SVGO version is no longer supported. Upgrade to v2.x.x.
12:05:22.105 ➤ YN0061: │ @babel/plugin-proposal-class-static-block@npm:7.13.11 is deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-static-block instead.
12:05:22.121 ➤ YN0061: │ @babel/plugin-proposal-json-strings@npm:7.13.8 is deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-json-strings instead.
12:05:22.122 ➤ YN0061: │ @babel/plugin-proposal-private-methods@npm:7.13.0 is deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-methods instead.
12:05:22.126 ➤ YN0061: │ @babel/plugin-proposal-private-property-in-object@npm:7.14.0 is deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-property-in-object instead.
12:05:22.162 ➤ YN0061: │ @babel/plugin-proposal-export-namespace-from@npm:7.12.13 is deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-export-namespace-from instead.
12:05:22.169 ➤ YN0061: │ @babel/plugin-proposal-logical-assignment-operators@npm:7.13.8 is deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-logical-assignment-operators instead.
12:05:22.175 ➤ YN0061: │ @babel/plugin-proposal-numeric-separator@npm:7.12.13 is deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead.
12:05:22.178 ➤ YN0061: │ @babel/plugin-proposal-nullish-coalescing-operator@npm:7.13.8 is deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.
12:05:22.185 ➤ YN0061: │ @babel/plugin-proposal-optional-catch-binding@npm:7.13.8 is deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-catch-binding instead.
12:05:22.200 ➤ YN0061: │ @babel/plugin-proposal-optional-chaining@npm:7.13.12 is deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.
12:05:22.208 ➤ YN0061: │ @babel/plugin-proposal-unicode-property-regex@npm:7.12.13 is deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-unicode-property-regex instead.
12:05:22.212 ➤ YN0061: │ @babel/plugin-proposal-async-generator-functions@npm:7.13.15 is deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.
12:05:22.217 ➤ YN0061: │ @babel/plugin-proposal-object-rest-spread@npm:7.13.8 is deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.
12:05:22.326 ➤ YN0061: │ is-accessor-descriptor@npm:1.0.0 is deprecated: Please upgrade to v1.0.1
12:05:22.326 ➤ YN0061: │ is-accessor-descriptor@npm:0.1.6 is deprecated: Please upgrade to v0.1.7
12:05:22.329 ➤ YN0061: │ is-data-descriptor@npm:1.0.0 is deprecated: Please upgrade to v1.0.1
12:05:22.329 ➤ YN0061: │ is-data-descriptor@npm:0.1.4 is deprecated: Please upgrade to v0.1.5
12:05:22.552 ➤ YN0061: │ stable@npm:0.1.8 is deprecated: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
12:05:22.654 ➤ YN0061: │ q@npm:1.5.1 is deprecated: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
12:05:22.654
12:05:22.654 (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
12:05:23.329 ➤ YN0032: │ evp_bytestokey@npm:1.0.3: Implicit dependencies on node-gyp are discouraged
12:05:23.779 ➤ YN0002: │ @vue/babel-plugin-jsx@npm:1.0.6 doesn't provide @babel/core (pe950c), requested by @babel/plugin-syntax-jsx
12:05:23.780 ➤ YN0000: │ Some peer dependencies are incorrectly met; run yarn explain peer-requirements <hash> for details, where <hash> is the six-letter p-prefixed code
12:05:23.781 ➤ YN0000: └ Completed in 6s 49ms
12:05:23.847 ➤ YN0000: ┌ Post-resolution validation
12:05:23.847 ➤ YN0028: │ The lockfile would have been modified by this install, which is explicitly forbidden.
12:05:23.847 ➤ YN0000: └ Completed
12:05:23.847 ➤ YN0000: Failed with errors in 6s 117ms
12:05:23.897 Error: Exit with error code: 1
12:05:23.897 at ChildProcess.<anonymous> (/snapshot/dist/run-build.js)
12:05:23.897 at Object.onceWrapper (node:events:652:26)
12:05:23.898 at ChildProcess.emit (node:events:537:28)
12:05:23.898 at ChildProcess._handle.onexit (node:internal/child_process:291:12)
12:05:23.906 Failed: build command exited with code: 1
12:05:24.929 Failed: error occurred while running build command
I'm wondering if it would be nice to move this deployments and hostings to Github Actions/Github Pages so it is accessible to all the maintainers. Any preference @roll ?
Hi, thanks! I think at least for v1 Github Pages would be better but I think we need to extract v1 to a new "legacy-code" repository first.