Add testing spec skeleton #2
Conversation
|
|
||
| Details: | ||
| - The `name` is an optional property. | ||
| - The `name` must be less than or equal to 214 characters. |
There was a problem hiding this comment.
Perhaps the existing npm docs can be copied as a starting point.
There was a problem hiding this comment.
yes, I was using part of it as a reference. I can port the docs easily if we agreed on it at #1 (comment) in a separate PR 😄
|
I think this PR should not land as is, and I honestly think the presence of this already here is jumping the gun. @UlisesGascon I am super happy to see your excitement, but I am worried that jumping right into implementation might cause legal or process issues for the effort. I think a better way to approach this would be to propose a set of things you would like to PR in an issue and then as this effort gets off the ground we can discuss and make sure we are not introducing any IP restrictions which would block this getting actual standards bodies involved. |
|
Thanks for the advice @wesleytodd 😉. I will close the PR for now until we are clear on how to move forward |
Main changes
Context
This skeleton is based on POC-semver-and-json-schemas
Changelog