It's a good idea to split base.rb in a file per class?

[patriciomacadden]

One class per file it's a good practice. I don't know if is a requirement that all core classes in sinatra resides in a single file?

Just wondering if would be nice to do this. It's not a big deal if it's not done, but maybe it would be nice.

It's so crazy what I'm saying?

[fr33z3]

I think it's a good idea.

[guiman]

👍

[JonRowe]

I'm a fan of this idea, but I think there might be a reason it's in one file, @rkh? I'm sure if you had a go at a pull request that @rkh would consider it @patriciomacadden ...

[patriciomacadden]

Of course I'll send a pull request if @rkh thinks it's a good idea. I don't want to do it if it's not.

[rkh]

No pull request, please. I'm not generally opposed to the idea, thought this has been discussed at length and might be overrated. Esp. since it right now is a big part of the Sinatra flair (main functionality is in one file and yet it's smaller than the readme). As you can see from the milestone, I am meaning to split it up for Sinatra 2.0.