status-im/EIPs
2
0
Fork 0
mirror of https://github.com/status-im/EIPs.git synced 2025-02-13 07:16:30 +00:00
Code Issues Projects Releases Wiki Activity

Update eip_validator to 0.8.2 (#2161)

Browse Source 
* Fix Markdown formatting in EIP-1186

* Update eip_validator to 0.8.2
This commit is contained in:
Alex Beregszaszi 2019-07-02 01:26:48 +01:00 committed by GitHub
parent 9608a9cfe5
commit 24c481d21e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
EIPS/eip-1186.md
View File

@ -142,7 +142,7 @@ Since this only adds a new Method there are no issues with Backwards Compatibili
## Test Cases ## Test Cases
<!--Test cases for an implementation are mandatory for EIPs that are affecting consensus changes. Other EIPs can choose to include links to test cases if applicable.--> <!--Test cases for an implementation are mandatory for EIPs that are affecting consensus changes. Other EIPs can choose to include links to test cases if applicable.-->
<TODO>Tests still need to be implemented, but the core function creating the proof already exists inside the clients and are well tested. TODO: Tests still need to be implemented, but the core function creating the proof already exists inside the clients and are well tested.
## Implementation ## Implementation
<!--The implementations must be completed before any EIP is given status "Final", but it need not be completed before the EIP is accepted. While there is merit to the approach of reaching consensus on the specification and rationale before writing code, the principle of "rough consensus and running code" is still useful when it comes to resolving many discussions of API details.--> <!--The implementations must be completed before any EIP is given status "Final", but it need not be completed before the EIP is accepted. While there is merit to the approach of reaching consensus on the specification and rationale before writing code, the principle of "rough consensus and running code" is still useful when it comes to resolving many discussions of API details.-->

2
Gemfile
View File

@ -31,4 +31,4 @@ gem "wdm", "~> 0.1.0" if Gem.win_platform?
gem "html-proofer", '>=3.3.1' gem "html-proofer", '>=3.3.1'
gem "eip_validator", ">=0.8.0" gem "eip_validator", ">=0.8.2"

4
Gemfile.lock
View File

@ -21,7 +21,7 @@ GEM
commonmarker (0.17.9) commonmarker (0.17.9)
ruby-enum (~> 0.5) ruby-enum (~> 0.5)
concurrent-ruby (1.0.5) concurrent-ruby (1.0.5)
eip_validator (0.8.0) eip_validator (0.8.2)
activemodel activemodel
front_matter_parser (~> 0.1.1) front_matter_parser (~> 0.1.1)
ethon (0.11.0) ethon (0.11.0)
@ -257,7 +257,7 @@ PLATFORMS
ruby ruby
DEPENDENCIES DEPENDENCIES
eip_validator (>= 0.8.0) eip_validator (>= 0.8.2)
github-pages github-pages
html-proofer (>= 3.3.1) html-proofer (>= 3.3.1)
jekyll (~> 3.6.2) jekyll (~> 3.6.2)