blockworks-foundation
/
mango-v4
mirror of https://github.com/blockworks-foundation/mango-v4.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

update 

Signed-off-by: microwavedcola1 <microwavedcola@gmail.com>
This commit is contained in:
microwavedcola1 2022-04-01 10:23:47 +02:00
parent 997301d079
commit 30ef479df9
2 changed files with 17 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
README.md
View File

@ -1,14 +1,22 @@
### Development ### Development
* rustc 1.57.0 (f1edd0429 2021-11-29)
* anchor-cli 0.22.0 - rust version 1.59.0 (9d1b2106e 2022-02-23)
* npm 8.1.2 - solana-cli 1.9.5
* node v16.13.1 - anchor-cli 0.22.0
- npm 8.1.2
- node v16.13.1
Devnet deployment - m43thNJ58XCjL798ZSq6JGAG1BnWskhdq5or6kcnfsD
TS client - see ts dir, and ts/example.ts, run as `yarn ts-node ts/example.ts`
### Module structure ### Module structure
As and when we move to a more complete project, we should think of having multiple modules As and when we move to a more complete project, we should think of having multiple modules
e.g. core/shared, spot, perpetuals, etc., and then each would have its own instructions e.g. core/shared, spot, perpetuals, etc., and then each would have its own instructions
and state sub module. Goal is that new contributors find relevant code easily and can navigate and state sub module. Goal is that new contributors find relevant code easily and can navigate
easily. easily.
``` ```
programs programs
└── mango-v4 └── mango-v4
@ -22,10 +30,11 @@ programs
│ ├── lib.rs │ ├── lib.rs
│ └── state # state goes here, each account state gets an individual file │ └── state # state goes here, each account state gets an individual file
│ └── mod.rs │ └── mod.rs
└── tests # rust tests, TODO └── tests # rust tests, TODO
``` ```
### How to open and manage pull requests ### How to open and manage pull requests
- when in doubt dont squash commits, specially when merge request is very large, specially if your branch contains unrelated commits - when in doubt dont squash commits, specially when merge request is very large, specially if your branch contains unrelated commits
- use the why along with what for commit messages, code comments, makes it easy to understand the context - use the why along with what for commit messages, code comments, makes it easy to understand the context
- add descriptions to your merge requests if they are non trivial, helps code reviewer watch out for things, understand the motivation for the merge request - add descriptions to your merge requests if they are non trivial, helps code reviewer watch out for things, understand the motivation for the merge request

7
ts/example.ts
View File

@ -28,12 +28,7 @@ async function main() {
); );
const admin = Keypair.fromSecretKey( const admin = Keypair.fromSecretKey(
Buffer.from( Buffer.from(JSON.parse(fs.readFileSync(process.env.KEYPAIR!, 'utf-8'))),
JSON.parse(
// 6pkqDeYxxnysUEvyhvXx1JWzWNoKQFSB95hYTxvHj4R3
fs.readFileSync(process.env.KEYPAIR!, 'utf-8'),
),
),
); );
const adminWallet = new Wallet(admin); const adminWallet = new Wallet(admin);