Re: [Rails] Rails conventions

2018-03-28 Thread Marco Antonio Almeida
Hi Brian, Here is an API reference for Rails: http://api.rubyonrails.org/. You need to check on the Rails version that you're using though, so you don't fall into missing or deprecated methods. There you can find an updated quick reference to the things that you probably dealt with like

Re: [Rails] Rails conventions

2018-03-27 Thread Brian Postow
by "not references" I meant it's way too verbose for what I need. The rails guides are meant (or appear to be meant) to be read cover to cover. I need something where I can looks a specific thing up. It's the difference between http://ruby-doc.com/docs/ProgrammingRuby/ and

Re: [Rails] Rails conventions

2018-03-27 Thread nanaya
On Wed, Mar 28, 2018, at 04:39, Brian Postow wrote: > The rails guides are not references. They're tutorials. > > An example of the thing I'm having trouble with: > > I'm having things like "it says it's missing foo_bar_bazes" but > "foo_bar_bazes" never occurs in my code, why does it think

Re: [Rails] Rails conventions

2018-03-27 Thread Walter Lee Davis
> On Mar 27, 2018, at 3:39 PM, Brian Postow wrote: > > No, I'm pretty sure that everything I'm looking at is strictly rails. A > friend pointed me at: > https://gist.github.com/iangreenleaf/b206d09c587e8fc6399e which is a really > good start. > > All of the conversions of

Re: [Rails] Rails conventions

2018-03-27 Thread Brian Postow
No, I'm pretty sure that everything I'm looking at is strictly rails. A friend pointed me at: https://gist.github.com/iangreenleaf/b206d09c587e8fc6399e which is a really good start. All of the conversions of CamelCase to snake_case, or plural to singular are all strictly rails. AFAIK, the

Re: [Rails] Rails conventions

2018-03-27 Thread Hassan Schroeder
On Tue, Mar 27, 2018 at 6:52 AM, Brian Postow wrote: > I'm an experienced programmer, who's starting to use Ruby on Rails for the > first time. I need some documentation that JUST explains how variable names > are manipulated. Things I need to understand: The questions you're