51–60 of 94 posts
I would love to see rails-api become a first-class player in the Rails ecosystem.
That said, other than increased usage, I don't think being included in core would actually do anything that we can't already do ourselves outside of core.
Hey 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.…
* the tension between 'rails' and 'rake' has always been there, and I see it trip up beginners. There is a gem that sorta does this, I'll give this some thought. * Making apps no longer a singleton has been happening on master already, so expect to see a bunch of that. * I like multipart emails too, since I prefer plaintext emails. * Working on the tokens issue, I already commented about it elsewhere in this thread.…
Hurray!
I consult for a number of startups, both at seed stage and with significant revenue. Mostly I do web applications, as opposed to "sites." I'm seeing more organizations learning towards frameworks like Ember.js and Angular.js. I'm also hearing lots of things like, "When I update the data in this browser, I want the changes to automatically propagate to other browsers." Among other things, this means I need robust plug…
I consult for a number of startups, both at seed stage and with significant revenue. Mostly I do web applications, as opposed to "sites." I'm seeing more organizations learning towards frameworks like Ember.js and Angular.js. I'm also hearing lots of things like, "When I update the data in this browser, I want the changes to automatically propagate to other browsers." Among other things, this means I need robust plug…
Thanks for asking! Are queues ready for prime-time yet? Another vote for async mailers please - also sending more than one mail at once would be nice. Sorting out secret_token.rb would be good - not sure what would work, ENV variable, auto-generating a file in production if not there, but there must be a better solution which lets you work both on Heroku and let's people avoid having secrets stored in version control…
The secret_token issue is one I'm personally interested in, we've been talking about the best way to fix it.
Yeah, we already have has_secure_password, which helps with authentication, but you still end up adding gems for authorization. I'll give this some thought, thanks.
Hey 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.…
Unicorns, ponies and rainbows please.
Simply adding `gem 'unicorn'` or `gem 'rainbows'` to your Gemfile will give you unicorns or rainbows, I'll investigate ponies, thanks.
Earlier quoted context omitted.
+1 for this. My team "rolls up" migrations akin to spring cleaning, because the migration files often have more important information that the db schema, and are easier for team members to learn quickly. I'll contribute $50 if this feature is accepted for Rails 4.1.
> I'll contribute $50 if this feature is accepted for Rails 4.1. Oh yeah? I wonder if others would also pay for bug bounties.