We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Updated Home (markdown)
Destroyed Config file draft (markdown)
Updated Release checklist (markdown)
Created Release checklist (markdown)
Change "keys" table to use "keys.global" instead of bare strings The TOML library I've been using (https://github.com/BurntSush/toml) parses TOML into a Go struct, which is handy as it allows for a fully typed config values, so you can do something like `Config.DefaultTimeout` instead of something like `Config.Get("defaultTimeout")`. The reason for the change is because this requires that the TOML layout be expressible with Go's types - one of the major differences between Go's type system and TOML's spec is that Go maps cannot have disparate values. Due to this, the previous keys layout would result in a type of `interface{}` for `Config.Keys`, eliminating any type-checking within it. The proposed structure would let us instead use the type `map[string] map[string]string`. It's a little confusing at first sight, but it just means you would access it using the following style: ```go Config.Keys["global"]["C-n"] Config.Keys["responseBody"]["C-s"] ``` This would remove the requirement to use either purely string-based configuration access or casting of `Config.Keys` to either `map[string] string` or `map[string] map[string]string` depending on whether you were accessing global or view-specific keys.
Updated Config file draft (markdown)
Update the paths to the config file for OSX (macOS) and Windows
Created Config file draft (markdown)
Initial Home page