Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

Remove unused @truffle/dashboard-provider module #5036

Merged
merged 1 commit into from
Apr 22, 2022

Conversation

benjamincburns
Copy link
Contributor

No description provided.

@benjamincburns benjamincburns force-pushed the remove-dashboard-provider branch 2 times, most recently from 0c8dac0 to 048c93f Compare April 20, 2022 04:01
Copy link
Member

@cds-amal cds-amal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. Deleting code is cathartic.


### Adding new message types

Right now there are very few message types. The most important one is `"provider"`, which sends RPC requests for the dashboard-provider. Other message types are `"invalidate"`, which can be sent to invalidate earlier messages, and `"log"`, which is sent by the message bus to send log messages over the wire. The interfaces of these messages are defined inside the `@truffle/dashboard-message-bus` package, from where they can be imported by consumers.
Right now there are very few message types. The most important one is `"provider"`, which sends RPC requests to the `@truffle/dashboard` so that they can be handled by the injected web3 provider that your wallet (e.g. MetaMask) provides. Other message types are `"invalidate"`, which can be sent to invalidate earlier messages, and `"log"`, which is sent by the message bus to send log messages over the wire. The interfaces of these messages are defined inside the `@truffle/dashboard-message-bus` package, from where they can be imported by consumers.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not for this PR, but we should document the message types, or add the current links that do.

@haltman-at
Copy link
Contributor

Note: This will incidentally address #5034. :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants