I wish there was some way to call the asset pipeline with parameters. E.g. "render that stylesheet with the dark theme".
Ask HN: What do you want to see in Rails 4.1?
21–30 of 94 posts
Re: Ask HN: What do you want to see in Rails 4.1?
#22I'm really missing deployment-specific settings, like `figaro` gem, especially for database.yml
Re: Ask HN: What do you want to see in Rails 4.1?
#23Maybe moving out secret key to .gitignored file, so that you can't (by default) commit it?
Re: Ask HN: What do you want to see in Rails 4.1?
#24[deleted]
Re: Ask HN: What do you want to see in Rails 4.1?
#25* Improved migration format: make it possible to create new initial migrations as a project evolves by rebasing. Meaning there's no need to keep or execute the whole migration history every time. On my current project running migrations from starch takes 30mins :( * Improvement in performance in regarding to JSON generation or other thing is always welcome. following benchmarks can be taken as reference where rails s…
I have seen people sorta 'merge up' migrations at a point in time...
As for JSON generation, there's an open ticket for it already: https://github.com/rails/rails/issues/9212
Re: Ask HN: What do you want to see in Rails 4.1?
#26Hey Steve, great of you to ask! Here are some suggestions: * Streamline the command line. Why rake to migrate, but rails to generate a migration? I know, I know. But new folks to Rails do not know. And it would be better if there was just one tool that does it all. * Get rid of the global magic functions. users_path is nice and sweet, but where is it defined? Object? Kernel? Why can't I just call a method on my app.…
Love the command line, queue, dotenv and log format suggestions.
Re: Ask HN: What do you want to see in Rails 4.1?
#27* Improved migration format: make it possible to create new initial migrations as a project evolves by rebasing. Meaning there's no need to keep or execute the whole migration history every time. On my current project running migrations from starch takes 30mins :( * Improvement in performance in regarding to JSON generation or other thing is always welcome. following benchmarks can be taken as reference where rails s…
Shouldn't you be using schema:load or structure:load rather than running your migrations from scratch? Migrations are for a database which already has data.
Re: Ask HN: What do you want to see in Rails 4.1?
#28Replace turbolinks with pjax.
Considering dhh created Turbolinks specifically to improve upon PJAX, I think we both know how likely that idea is. Thanks for the suggestion though!
More realistically, commenting it by default would be IHMO a good idea.
A friend of mine who currently learn rails and angular by himself got bitten by it. And angular is definitely not the only JavaScript framework / plugin that don't work well with Turbolinks.
It's a very nice gem for some use cases but a terrible default.
Re: Ask HN: What do you want to see in Rails 4.1?
#29Thanks for asking Steve! I think Rails is already very complete. I would like to see an included state machine, rails-api integration, commands (baby-zeus) integration and GitLab secret storage ( https://github.com/gitlabhq/gitlabhq/pull/4040 ). But I realize these are all very controversial. The most important thing is the core-team stays happy, so no problem if these can't make it.
What is baby-zeus? I'm personally very interested in the secret_token issue, and so is the rest of the team, but it's tricky to get the balance right. Working on it!
With baby-zeus I mean https://github.com/rails/commands. The secret_token is indeed hard, other people proposed the dotEnv gem which makes sense as well. Or maybe link a whole directory to a shared dir?
Re: Ask HN: What do you want to see in Rails 4.1?
#30What do you think about integrating https://github.com/charliesome/better_errors directly into rails?
Very good suggestion, this should be default.