People
 :bowtie: |
😄 :smile: |
😆 :laughing: |
|---|---|---|
😊 :blush: |
😃 :smiley: |
:relaxed: |
😏 :smirk: |
😍 :heart_eyes: |
😘 :kissing_heart: |
😚 :kissing_closed_eyes: |
😳 :flushed: |
😌 :relieved: |
😆 :satisfied: |
😁 :grin: |
😉 :wink: |
😜 :stuck_out_tongue_winking_eye: |
😝 :stuck_out_tongue_closed_eyes: |
😀 :grinning: |
😗 :kissing: |
😙 :kissing_smiling_eyes: |
😛 :stuck_out_tongue: |
As a developer, I need to start with a story.
A few sentences describing the overall goals of the pull request's commits. What is the current behavior of the app? What is the updated/expected behavior with this PR? Include your acceptance critiera! If your tasks were well-written, you can probably copy/paste some of this.
I hereby claim:
To claim this, I am signing this object:
In my feedback I’m defining things this way:
Ultimately… I think the editor navigation would make more sense with a “rule” that tabs move you from “unit” to “unit”, and arrows move you within (and between, if they are nested) sections/units. It gives the interaction more of a consistent rule and I feel like it would help because people are transitioning between mental states if they’re perusing a list of Items vs jumping from Recent to Embed, for example.
