Move some issues to wiki

[JoshCheek]

Some issues really belong in "potential future features" https://github.com/JoshCheek/seeing_is_believing/wiki/Potential-future-features so they're not sitting around growing stale in the issues list.

[ckib16]

@JoshCheek - I'll be happy to help. Would you mind just flagging which issues you'd like transferred to wiki?

Maybe we could do something like:

• I move the issue to wiki
• You check it all looks good & close the original issue?

[JoshCheek]

Note: probably cross link from that page to the closed issue to give it some context.

See #113 for info about being a contributor, which is necessary to manage issues.

K = Keep it in the issues, M = Move it to the wiki

• K Better home page for the wiki
• K Move some issues to wiki
• K Move overrides into Haiti

• * M Change the event consumer to allow multiple event streams

• K Use a default inspect? (this is pretty low-hanging fruit, so I'll leave)
• K Make sure multiple assignment in 2.4 works correctly
• K Spacemacs integration (I haven't actually read through that thread, but it would be valuable to get SiB added to an editor by default, so I should go check it out)

• * M Don't align values if there's too much whitespace (it's irritating when you hit it, but that's honestly not super common, and that is a sufficient reminder to not need to keep the issue open)

• K Void Value Expressions
• K Heredoc woes (really, this should go, but it's a bug and I'm worried I might forget about it if I move it out of sight)
• K Does not record else block if not part of a rescue (this is almost resolved)

• * M Maybe idea for a better evaluator
• * M Use backtrace location

• K Requiring a file outputs error (this should probably be converted into a different issue, ie if there is something that should be done about it then open a new issue for that thing)

• * M Get it working for JRuby and Rubinius (the cost of this is high and the value is low due to their startup times, so we'll move it... although it's probably a lot easier now that we have it working on Windows)
• * M Allow arbitrary flags to be passed to the bin

• K I NEED JOSH CHEEK FROG PERSON STICKERS This makes me happy, so we'll leave it where I can see it and boost my mood every now and then ^_^

(note to self in case I need to regenerate this list: cache curl -s 'https://api.github.com/repos/JoshCheek/seeing_is_believing/issues' | jq 'map({html_url, title})[]' -c | ruby -ne 'i=eval $_; puts "* **M** [#{i[:title]}](#{i[:html_url]})"')

[ckib16]

Great! Thanks for the detailed list.

I'll try to start working a PR tomorrow.

I'll probably do a PR with this 1st one vs edit wiki in place (which is what I normally do). Just so you can see if you like the changes.

EDIT 2017-01-20

• I meant:
  • For Wiki - I will develop locally, and push up the wiki changes. My mistake (GH does not allow an easy way to do PRs for wikis)

[ckib16]

Ok @JoshCheek - I added a new section for this in the wiki sidebar.

Let me know if this meets your intent. Then we can just close out the issues checked off above

--UPDATE
I think I just realized your intent to move these issues marked above to the "potential future features" page as you stated. My mistake. Updating now.

[ckib16]

Ok - NOW it's done :)

If good, we can just

• close out the 6 issues marked above
• close out this issue

[JoshCheek]

Looks good to me :)

[JoshCheek]

You can go ahead and close them (I obviously could do this, too, but letting you do it emphasizes your efficacy)

[ckib16]

Gotcha - closing now. Just wanted to keep them open until you had a look.

[JoshCheek]

I came to check in on the issues, and there were so many fewer of them, ty ^_^

[ckib16]

Hah - no worries man. Yeah, I bet it looks a bit more manageable for you now.