- Search for photo by viewing on unsplash.com and finding ID in URL. For example https://unsplash.com/photos/photo-of-green-leafed-plants-QKo-op_gR9I which has ID
QKo-op_gR9I
- Grab your access key from Unsplash API dashboard:
ACCESS_KEY_GOES_HERE
- Grab JSON file by plugging in ID and client_id into API so URL looks like this: https://api.unsplash.com/photos/QKo-op_gR9I?client_id=ACCESS_KEY_GOES_HERE
- Pull out the regular size URL from the JSON in "urls > regular" key (which is 1080 wide) and use that in the site
- Primarily highlight content author. Inlude a PFP image, name, organization name and a link to their personal site.
- Secondarily highlight all reviewers and contributors
- Link to a specific topic on Peeranha forum so users can ask questions and have discussions. For example Lesson 4: Testing your TierNFT would point to Testing Solidity contracts topic in Peeranha.
Other goals:
- Create a consistent header and footer to use for all content tracks and fundamentals
- Add a general link to our Peeranha community in Footer and Getting Started - https://developerdao.peeranha.io
Follow instructions here: https://gist.github.com/Beneboe/3183a8a9eb53439dbee07c90b344c77e
When you merge commits via GitHub UI (say "squash and merge"), GitHub will sign the commit itself.
Import GitHub webflow key so key is verified when you run git log --show-signature
- In Rust, add
msg!("Some variable: {:?}", variable);
- Run
anchor test
to run the program through the tests. However you won't find the output there. - View the output instead in a file within your
program-logs
folder in your Anchor project. It'll be recreated each time you run the program.
This is subtly mentioned in the docs and can be found in the CLI docs here: https://book.anchor-lang.com/chapter_4/cli.html#test
The https://github.com/Developer-DAO/pixel-avatars project has a non-standard place for the contracts so the OpenZeppelin imports are shown with a red lint error.
For Solidity VSCode plugin, set "Package Default Dependencies Directory" to contract/node_modules
instead of default node_modules
.
VSCode can then find the OpenZeppelin imports.
html { | |
font-family: -apple-system, BlinkMacSystemFont, Segoe UI, Roboto, Oxygen, | |
Ubuntu, Cantarell, Fira Sans, Droid Sans, Helvetica Neue, sans-serif; | |
} | |
.code { | |
font-family: Menlo, Monaco, Lucida Console, Liberation Mono, DejaVu Sans Mono, | |
Bitstream Vera Sans Mono, Courier New, monospace; | |
} |
interface Props { | |
clickOnSuccess: ( | |
event: React.MouseEvent<HTMLButtonElement>, | |
url: string | |
) => void; | |
} |
For those new to Minecraft Plugins, there's a lot of new and old documentation to run through on the web.
Additionally plugins compiled on newer versions of Java weren't working on older stable Minecraft server versions.
I've captured my learning in two places:
- This guide covers the workflow of editing, compiling and testing plugins.