Review FDC3 npm module (particularly methods.ts) and update for FDC3 2.0
Prior to release the FDC3 source and NPM module need to be updated for any new or updated functionality added or changed in 2.0 (e.g. new API calls, API calls that became async, deprecation flags that should be added to API types etc.).
While I agree we definitely need this, is there any chance we could have a different milestone for it? It's not a specification change and it's throwing out the roadmap.
Maybe 2.0-completion or something?
EDIT: or maybe just remove the api tag.
Added a 2.0-release-tasks milestone and added it (and couple of similar issues) to it.
Fixed a bunch of missing exports for new types and issued a temporary 2.0.0-beta.2 version on NPM (change the version number in the root packaage.json and the github action will build and release as latest automatically).
@rikoe have you got time to complete this review in the next couple of weeks and think about whether we can set up an action to build and push a 'next' version to npm (that is not set as 'latest' - as is the case with the current github action) on merge to the trunk?
resolved by #951