-
Notifications
You must be signed in to change notification settings - Fork 5.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
1193: Final edits in response to feedback #2695
Conversation
EIPS/eip-1193.md
Outdated
@@ -15,12 +15,10 @@ requires: 155, 695 | |||
|
|||
This EIP formalizes a JavaScript Ethereum Provider API for consistency across clients and applications. | |||
|
|||
The Provider's interface is designed to be minimal, preferring that features are introduced in the API layer (see e.g. [`eth_requestAccounts`](https://eips.ethereum.org/EIPS/eip-1102)), and agnostic of transport and RPC protocols. | |||
The Provider's interface is designed to be minimal and agnostic of transport and RPC protocols. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My intention with these words were for implementers to keep away from extending and adding their own methods and properties to the provider object as it just causes confusion and fragmentation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The new text will be as follows, and I do think that it conveys that new functionality can be added via new RPC methods.
The Provider's interface is designed to be minimal, event-driven, and agnostic of transport and RPC protocols.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added back updated language reflecting goals in ffe92ce
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thanks!
ffe92ce
to
ff39c4a
Compare
Hi, I'm a bot! This change was automatically merged because: - It only modifies existing Draft or Last Call EIP(s) - The PR was approved or written by at least one author of each modified EIP - The build is passing
Hi, I'm a bot! This change was automatically merged because: - It only modifies existing Draft or Last Call EIP(s) - The PR was approved or written by at least one author of each modified EIP - The build is passing
Hi, I'm a bot! This change was automatically merged because: - It only modifies existing Draft or Last Call EIP(s) - The PR was approved or written by at least one author of each modified EIP - The build is passing
Link to file: https://github.com/rekmarks/EIPs/blob/1193-final-draft/EIPS/eip-1193.md
Events
specificationEventEmitter
from normative to non-normativeEventEmitter
API, while stable is growing over timemessage
event "Subscription" subsection in API documentation