OpenST developer-guidelines issues

OpenST / developer-guidelines

Guidelines on code, project setup, etc.

MIT License

3 stars 8 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Introduces a new naming convention for interfaces and abstract contracts.

#34 pgev closed 4 years ago
1
Update solidity style guide wrt documenting an author for a contract

#33 pgev opened 5 years ago
0
Create typescript developer guidelines.

#32 deepesh-kn opened 5 years ago
1
Reminder: fix lint issues.

#31 deepesh-kn opened 5 years ago
0
check all repos use SafeMath as NPM from OpenZeppelin

#30 benjaminbollen opened 5 years ago
0
Specify which labels to use

#29 schemar closed 5 years ago
0
Deduplicate ERC20 Token

#28 schemar opened 5 years ago
2
Publish organization and utility tokens as npm package

#27 schemar opened 5 years ago
0
Branch protection settings should be aligned across repositories

#26 schemar opened 5 years ago
0
Manage internal and external dependencies

#25 gulshanvasnani closed 5 years ago
2
Added checks effects interactions in security section

#24 0xsarvesh closed 5 years ago
1
Steps for releases

#23 gulshanvasnani opened 5 years ago
1
Clarify definition(s) of "value token"

#22 jasonklein opened 5 years ago
0
Added proposal for JS logging

#21 0xsarvesh closed 5 years ago
1
Deduplicate code

#20 schemar opened 5 years ago
9
Use resources from developer guidelines

#19 schemar opened 5 years ago
0
npm publishing

#18 schemar opened 5 years ago
0
Add pull request guidance

#17 jasonklein closed 5 years ago
6
Add section on ports

#16 schemar closed 5 years ago
0
push tag on master and publish NPM 0.10.0

#15 benjaminbollen closed 5 years ago
7
🤵 Formalize the release process

#14 benjaminbollen opened 5 years ago
1
write release notes on Github for 0.10

#13 benjaminbollen closed 5 years ago
2
Default ports should be non-conflicting

#12 schemar closed 5 years ago
0
Changelog management

#11 schemar closed 5 years ago
0
Old contract repositories should be deprecated

#10 schemar closed 5 years ago
1
NPM Publish must be aligned across all repositories

#9 schemar opened 5 years ago
0
Unfinished issues should comment their state

#8 schemar closed 5 years ago
0
Labels should be unified across repositories

#7 schemar closed 5 years ago
12
Should we use require with a meaningful message in addition to SafeMath?

#6 schemar closed 5 years ago
0
Solidity order of execution should be documented

#5 schemar closed 5 years ago
0
Include warning for npm install with webpack

#4 schemar closed 5 years ago
0
Update English Sentence style guidance.

#3 jasonklein closed 5 years ago
0
Unified logging

#2 schemar closed 5 years ago
2
Handling of internal and external dependencies of packages

#1 benjaminbollen closed 5 years ago
2