Kris West

@thorsent @ggeorgievx @rikoe For the System channels -> User channels rename, where functions changed name (e.g. `getSystemChannels()` -> `getUserChannels()`) we implemented [an automated fallback in the NPM Module's Methods.ts](https://github.com/finos/FDC3/blob/1625a550ceb4fba60af32b7b61ab50b84bf5c308/src/api/Methods.ts#L82-L112). There's...

On returning to this issue, I am less sure about the proposed change (allowing for a display name per intent/app combo). There are situations (e.g. a button to raise an...

Notes from #802: - The AppIntent interface only allows for a single display name to be returned. However, the main source for the display name is the interop/intents configuration of...

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...

Kris / Cosaic 🚀

@nkolba it'd be interesting to hear what you use these endpoints for and the functionality they have in electron-fdc3 @Qiana-Citi @RandallDang-Citi likewise it'd be really interesting to hear more about...

> @kriswest We are looking into this to be able to dynamically show to the user the locally available intents/apps on a fdc3 object. > This fdc3 object could be...

Notes from #802: - A number of participants (including @nkolba and @kriswest) felt that the proposed `/intents` and `/contexts` appD endpoints are useful for both development and governance use (at...

We've also be brainstorming alternatives with 'single channels' but with a direction that the end-user can specify. The developer can (sort of) do that by just not listening OR not...