atd issueshttps://staging.gitlab.com/izwick-schachter/atd/-/issues2017-06-29T11:39:46Zhttps://staging.gitlab.com/izwick-schachter/atd/-/issues/34**arument_hash notation2017-06-29T11:39:46Zusername-removed-662768**arument_hash notationWe should upgrade the codebase to use `**args` instead of `*args` in some cases, because `**args` only takes the hash arguments, whereas `*args` will also take normal args.We should upgrade the codebase to use `**args` instead of `*args` in some cases, because `**args` only takes the hash arguments, whereas `*args` will also take normal args.v0.6.0https://staging.gitlab.com/izwick-schachter/atd/-/issues/33String keys in settings hash added to headers2017-06-29T11:39:46Zusername-removed-662768String keys in settings hash added to headersI think that whenever an option is passed in the settings hash with a string as the key, that key/value pair should be added to the settings hash and also should be added to the headers. This would resolve all that's left of #25, and wou...I think that whenever an option is passed in the settings hash with a string as the key, that key/value pair should be added to the settings hash and also should be added to the headers. This would resolve all that's left of #25, and would just seem to make sense.v0.6.0https://staging.gitlab.com/izwick-schachter/atd/-/issues/32New Default App Test Failing2017-06-29T11:39:46Zusername-removed-662768New Default App Test FailingWIPWIPv0.5.0https://staging.gitlab.com/izwick-schachter/atd/-/issues/31Different file parsing in request v. verb2017-06-29T11:39:46Zusername-removed-662768Different file parsing in request v. verb## MCVE
```ruby
require "atd" # Development branch
get "/", "Hi"
r "/not-working", "Hi"
start
# get("/").body == "Hi"
# get("/not-working").body == ""
```## MCVE
```ruby
require "atd" # Development branch
get "/", "Hi"
r "/not-working", "Hi"
start
# get("/").body == "Hi"
# get("/not-working").body == ""
```v0.5.0username-removed-662768username-removed-662768https://staging.gitlab.com/izwick-schachter/atd/-/issues/30Use refinements instead of global monkey-patching core classes.2017-06-29T11:39:46Zusername-removed-662768Use refinements instead of global monkey-patching core classes.In `builtin_class_modifications.rb` we modify `Hash` and `Object`, those should be refinements instead.In `builtin_class_modifications.rb` we modify `Hash` and `Object`, those should be refinements instead.v0.5.0username-removed-662768username-removed-662768https://staging.gitlab.com/izwick-schachter/atd/-/issues/29Should url's be case sensitive by default?2017-06-29T11:39:46Zusername-removed-662768Should url's be case sensitive by default?They should definitely have the option to be case sensitive, but the question is: what should the default be?They should definitely have the option to be case sensitive, but the question is: what should the default be?v0.6.0username-removed-662768username-removed-662768https://staging.gitlab.com/izwick-schachter/atd/-/issues/28Simplify Exposing Assets2017-06-29T11:39:46Zusername-removed-662768Simplify Exposing AssetsSometimes you have a lot of files that you want to expose with their file names as the path. Some easy ways to accomplish that would be to allow multiple get routes to be created with notation such as `get ["asset1.png", "asset2.css", "a...Sometimes you have a lot of files that you want to expose with their file names as the path. Some easy ways to accomplish that would be to allow multiple get routes to be created with notation such as `get ["asset1.png", "asset2.css", "asset3.js"]` or to simply make it possible to expose an entire folder: `expose "MyFolder", "css"` than make it accessable as `get "/myCssFile", css: "myfile.css"` (Actually there is probobly a better alternative to the second one, because that would add it to the opts hash). Think about it!v0.6.0https://staging.gitlab.com/izwick-schachter/atd/-/issues/27Pass Settings Hash To Compilation Methods2017-06-29T11:39:46Zusername-removed-662768Pass Settings Hash To Compilation MethodsMakes developing them easier.Makes developing them easier.v0.5.0username-removed-662768username-removed-662768https://staging.gitlab.com/izwick-schachter/atd/-/issues/26Tilt?2017-06-29T11:39:46Zusername-removed-662768Tilt?https://staging.gitlab.com/izwick-schachter/atd/-/issues/25Allow mime-type to be specified2017-06-29T11:39:47Zusername-removed-662768Allow mime-type to be specifiedIt should be possible to specify mime-type in compiler methods which can be overridden by the route options hash.It should be possible to specify mime-type in compiler methods which can be overridden by the route options hash.v0.6.0username-removed-662768username-removed-662768https://staging.gitlab.com/izwick-schachter/atd/-/issues/24Be ready for 2.42017-02-08T02:37:36Zusername-removed-662768Be ready for 2.4Our tests assert things are equal to Fixnum when they should be integer as an example. Make sure we will be fine in 2.4, check the everything, use preview releases.Our tests assert things are equal to Fixnum when they should be integer as an example. Make sure we will be fine in 2.4, check the everything, use preview releases.v0.5.0https://staging.gitlab.com/izwick-schachter/atd/-/issues/23README Rewrite2017-02-08T02:38:38Zusername-removed-662768README Rewritev0.5.0https://staging.gitlab.com/izwick-schachter/atd/-/issues/19Allow alternative methods to match routes2017-02-27T02:19:09Zusername-removed-662768Allow alternative methods to match routesIn sinatra for example routes can be matched with regex and other methods. Check other ways in sinatra.In sinatra for example routes can be matched with regex and other methods. Check other ways in sinatra.v0.6.0https://staging.gitlab.com/izwick-schachter/atd/-/issues/18Make @http into a collection of methods2017-02-08T02:37:00Zusername-removed-662768Make @http into a collection of methodsInstead of using `@http` we should expose everything similar to how the `params` "hash" (not actually a hash) is exposed in sinatra, where it is actually a method defined in `main`. This would also allow us to resolve #16. Additionally i...Instead of using `@http` we should expose everything similar to how the `params` "hash" (not actually a hash) is exposed in sinatra, where it is actually a method defined in `main`. This would also allow us to resolve #16. Additionally it may be useful to expose it on a class by class basis as well as in `DefaultApp`.v0.5.0https://staging.gitlab.com/izwick-schachter/atd/-/issues/17Allow sinatra style compilation.2017-06-29T11:39:47Zusername-removed-662768Allow sinatra style compilation.We should allow Sinatra style compilation and make in route compilation (#13) a long term option. That has proven challenging to implement.We should allow Sinatra style compilation and make in route compilation (#13) a long term option. That has proven challenging to implement.v0.4.0https://staging.gitlab.com/izwick-schachter/atd/-/issues/15Allow the return value to be the output2017-06-29T11:39:47Zusername-removed-662768Allow the return value to be the outputIt would make logical sense if when `request` was given only a path and no output, that it would automatically use the return value as output. Beware! This could become a security issue. So
```ruby
get "/" do
"hi"
end
```
should retu...It would make logical sense if when `request` was given only a path and no output, that it would automatically use the return value as output. Beware! This could become a security issue. So
```ruby
get "/" do
"hi"
end
```
should return `hi`v0.4.0username-removed-662768username-removed-662768https://staging.gitlab.com/izwick-schachter/atd/-/issues/14Unclear what route[:block] refers to2017-06-29T11:39:47Zusername-removed-662768Unclear what route[:block] refers toAs I mentioned in the first commented on #13, it's really confusing that `route[:block]` is the instance method which is created instead of just storing the block.As I mentioned in the first commented on #13, it's really confusing that `route[:block]` is the instance method which is created instead of just storing the block.v0.4.0https://staging.gitlab.com/izwick-schachter/atd/-/issues/11Cannot access Rack::Response through @http2017-06-29T11:39:47Zusername-removed-662768Cannot access Rack::Response through @httpThis is a vital function.This is a vital function.v0.4.0username-removed-662768username-removed-6627682016-11-03https://staging.gitlab.com/izwick-schachter/atd/-/issues/10Space Notation2017-06-29T11:39:47Zusername-removed-662768Space NotationIt would be much nicer to add to the dot syntax (`r.get.post.path`) a new space syntax, which is the exact same with only spaces and much start with an http method, e.g. `get post put "/", "Hi"`.It would be much nicer to add to the dot syntax (`r.get.post.path`) a new space syntax, which is the exact same with only spaces and much start with an http method, e.g. `get post put "/", "Hi"`.username-removed-662768username-removed-662768https://staging.gitlab.com/izwick-schachter/atd/-/issues/9Status codes don't appear2017-06-29T11:39:47Zusername-removed-662768Status codes don't appearWhen you make a request with the `r`, `req` or `request` syntax, there is no status code in the response.When you make a request with the `r`, `req` or `request` syntax, there is no status code in the response.v0.4.0