Problem/Motivation
Publish vertical slice POC on NPM to make it easier for developers to experiment and provide feedback.
Under what namespace would it make sense to publish this? It won't be @drupal
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork api_client-3391145
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
brianperryThings to consider here:
* Should we implement changesets prior to publishing?
* Should we adopt conventional commits - https://www.conventionalcommits.org/en/v1.0.0/
* Will it be possible to automate this process before we're under the Drupal namespace? Will we have to mirror the codebase somewhere? Or publish manually?
Comment #3
brianperryVersioning while working on 1.x. I'm now thinking we should keep this simple. Publish an initial 0.x version representing the POC. We can then declare that specific version as the vertical slice POC version. Beyond that, we can keep working on 1.0 and publishing our ongoing work as incremental 0.x releases until we complete our scope for 1.0.
Comment #4
brianperryEnsuring publishing is based on main, and docs publishing is based on main as well.
Comment #6
brianperryHad to make more changes than I expected here as a result of the package namespaces changing. Should be close, but tsc is now complaining about:
Any ideas?
Comment #8
brianperryPublished as
https://www.npmjs.com/package/@drupal-api-client/api-client/v/0.1.0
and
https://www.npmjs.com/package/@drupal-api-client/json-api-client/v/0.1.0
Created a quick codesandbox to sanity check the release: https://codesandbox.io/s/drupal-api-client-json-api-client-basic-example...
Creating @coby.sher for help debugging.
Comment #9
cosmicdreams commentedOn the NPM page, it might be helpful to publish a user story / user stories that help people know that this vertical slice either addresses or doesn't address their use case.
It's difficult to know what scenarios this would be used for, with just the NPM page's documentation.