Erik Kundt
50c22f0800
Adds script which compiles docs example with minimum compiler version.
2020-03-18 19:27:38 +01:00
William Entriken
6d068b6331
Reduce usage of the word "kill"
2020-01-07 11:18:10 +01:00
Chris Chinchilla
f46218cad9
Update pragma versions for 0.6.0
2019-12-16 17:36:44 +01:00
Leonardo Alt
3198f55d24
Docs style guide
2019-12-13 12:40:33 +01:00
Mathias Baumann
5b8ff78176
Implement virtual keyword
2019-11-14 11:49:39 +01:00
Daniel Kirchner
3321fc56ea
Split fallback function and introduce "fallback()" and "receive()" syntax.
2019-11-04 17:17:58 +01:00
Alexander Arlt
cd3ad73b5a
Update tests.
2019-11-01 14:54:47 -05:00
Mathias Baumann
6c6a9054b2
Implement override checking
2019-10-30 17:31:33 +01:00
chriseth
57def9e8b4
Merge pull request #7395 from balajipachai/patch-2
...
Fixed typo at the end of the file
2019-09-10 12:29:49 +02:00
Balaji Pachai
27fb79dc10
Fixed typo at the end of the file
...
Changed `annontated` to `annotated`
2019-09-10 15:52:06 +05:30
Balaji Pachai
8fe4fe7921
Fixed a typo
...
Replaced is with in to make the statement grammatically correct.
2019-09-10 15:35:52 +05:30
Balaji Pachai
45d6d4567e
Fixed a typo
...
Changed proceeded to preceded, making the statement grammatically correct.
2019-09-10 15:17:58 +05:30
Chris Chinchilla
f99d78117e
Bring code examples for Style Guide inline with style guide
...
Add back accidentally removed public
2019-06-05 15:25:18 +02:00
William Entriken
f1be1b2758
Learn how to spell section
2019-05-29 21:02:03 -04:00
William Entriken
916e151f46
Add NatSpec documentation.
2019-04-19 00:54:08 +02:00
chriseth
8d401ba936
Update pragmas.
2019-03-05 18:10:09 +01:00
Chris Ward
0c1affe43e
Begin documentation style guide
...
Add pragma to documentation style guide
Fix formatting and add link
Move docs style guide
Changes from review
2019-02-27 11:48:51 +01:00
Ricardo Guilherme Schmidt
c7e0965801
Add NatSpec to Style-Guide
...
related to #2270
2018-12-12 16:51:28 +01:00
Chris Ward
bbe0268163
Add mapping guide to style docs thanks to @aupiff
2018-12-03 10:43:53 +01:00
Alex Beregszaszi
3ca00c73f9
Update version pragma in all documentation examples
2018-09-25 19:03:25 +01:00
Alex Beregszaszi
6f758a6c95
Include pragma in 'Order of Layout' in the style guide
2018-09-18 15:06:49 +01:00
Chris Ward
98bc9ac326
Added order of layout to style guide
2018-09-18 15:37:16 +02:00
chriseth
8a06000a30
Update documentation.
2018-08-14 15:50:46 +02:00
Luke Schoen
835c05cb3a
Update style guide with regards to CapWords requirement for contract and file naming.
2018-08-06 18:23:58 +02:00
Cryptomental
eb92d5f760
docs: Fix typos.
...
Used codespell and manual fixes.
Refs: #4442
2018-07-10 22:57:59 +02:00
Leo Arias
8fdf3f5d45
update the style guide
2018-07-04 04:29:00 +00:00
chriseth
eeef82b2d7
Fallback function has to be external: backwards-compatible changes.
2018-06-29 00:23:52 +02:00
Daniel Kirchner
1a014f83cc
Prefer view over constant in the documentation.
2018-05-09 15:06:47 +02:00
Leo Arias
aff19a1009
docs: clarify the maximum line length style
2018-04-24 10:27:35 -06:00
wbt
8aadc179ae
Fix small formatting issue
...
in which a constant was not treated as code, inconsistent with surrounding examples.
2018-03-30 15:28:15 -04:00
chriseth
cf6720eab5
Merge pull request #3587 from OTTTO/develop
...
Multiline output parameters and return statements
2018-03-01 12:07:09 +01:00
Dax Bondye
e34d367593
Multiline output parameters and return statements
2018-02-26 19:32:55 -08:00
chriseth
97d1c70491
Merge pull request #3575 from OTTTO/develop
...
Recommend to explicitly label the visibility of functions.
2018-02-22 22:41:29 +01:00
Dax Bondye
2ac49b3c2d
Reccomend to explicitly label the visibility of functions.
2018-02-22 10:23:20 -08:00
chriseth
71a34abd87
Merge pull request #3513 from OTTTO/develop
...
Add "Maximum Line Length" section
2018-02-22 16:12:49 +01:00
DYLAN BECKWITH
187e50b14c
Recommend consistent style for wrapping long lines.
2018-02-22 07:01:07 -08:00
William Entriken
5497a85158
Clarify name documentation for mixedCase
2018-01-29 14:45:36 -05:00
wbt
1948b9687f
Case convention clarification
...
Constructors follow the contract naming convention, using CapWords, instead of mixedCase.
2018-01-16 13:08:20 -05:00
William Entriken
cb5758aa75
Prefer CapWords style struct names
2018-01-14 13:53:45 -05:00
Jim McDonald
6e521d59b0
Fix Solidity warnings
2017-12-12 18:47:30 +00:00
Kamuela Franco
ef57961711
Update style-guide.rst to include enum style
2017-12-09 14:53:40 +00:00
Christian Pamidov
f9b240096f
Fixed typos ( #3139 )
2017-10-28 12:48:57 +01:00
Svetlin Nakov
58778be567
Fixed typos
2017-10-25 22:58:18 +03:00
Svetlin Nakov
f39cf7be41
Improved the "Naming" section
...
Improved the "Naming" section. Added naming examples. Improved consistency.
2017-10-25 10:33:26 +03:00
Alex Beregszaszi
2d8b0fdc39
Fix inconsistent use of single backticks
2017-03-15 23:41:02 +00:00
ethers
217f33c252
Clearer language as suggested by @axic
2016-11-22 00:47:58 -08:00
ethers
feebe3e755
Fallback functions don't always have to be payable
2016-11-17 18:14:26 -08:00
ethers
1d9aee97c2
styleguide: Don't include a whitespace in the fallback function
2016-11-17 18:13:33 -08:00
ethers
549bca1494
Don't include a whitespace in fallback function
2016-11-17 18:09:22 -08:00
ethers
39559c1bb6
styleguide: Ordering of functions
...
Ordering would help readers identify which functions they can call, and to find the "specials" (constructor and fallback function). Mixing the "specials" in the middle of the code, as well as internal functions between external and public functions, don't help readers
Based on https://github.com/ConsenSys/MultiSigWallet/issues/19
2016-11-17 18:06:28 -08:00
