-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds an optional config section to the help ouput for bundles #1011
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,6 +8,13 @@ defmodule Cog.Chat.Slack.Templates.Embedded.HelpBundleTest do | |
"commands" => [%{"name" => "test-command", | ||
"description" => "does just one thing"}], | ||
"author" => "vanstee", | ||
"config_file" => %{ | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This feels a little weird. I know we don't have a db column for this stuff, but it'd still be nice if we rendered it all as if it was one. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not sure I understand. Are you saying that we should add virtual fields for the config bits? I don't think that would change the test here, would it? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Oh I think I misunderstood what was going on here. But it still seems weird that we need access to the |
||
"config" => %{ | ||
"notes" => "Some notes about config", | ||
"env" => [%{"var" => "VAR1", "description" => "description1"}, | ||
%{"var" => "VAR2"}] | ||
} | ||
}, | ||
"homepage" => "test-bundle.com"}]} | ||
|
||
|
||
|
@@ -20,6 +27,13 @@ defmodule Cog.Chat.Slack.Templates.Embedded.HelpBundleTest do | |
|
||
No really, it does a thing | ||
|
||
*Configuration* | ||
|
||
Some notes about config | ||
|
||
• VAR1 - description1 | ||
• VAR2 | ||
|
||
*Commands* | ||
|
||
• test-command - does just one thing | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since config is typically "set and forget" I think it should probably go near the bottom. Maybe just above the homepage and author.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's actually why I put it at the top. I was thinking that the most important stuff was the command bits and I didn't want them to get pushed off the screen.