> On March 26, 2019, a malicious version of the popular #bootstrap#sass package, that has been downloaded a total of 28 million times to date, was published to the official #RubyGems repository. Version 3.2.0.3 includes a stealthy backdoor that gives attackers remote command execution on server-side #Rails applications.
I'm gonna impose the restriction upon myself that I'm not going to come up with or entertain any business ideas until I learn the ins and outs of #Rails. #personal
I think I'm up against a polymorphic association in #Rails, and Jesus Christ, is it ever daunting.
Trying to fetch all answers made by a user for a particular question. Fetching the answers works, fetching the questions works. But I can't seem to do this in a way that question.query and answer.body are displayed together in a coherent fashion.
What I need is to display a question title with a link to the question, then display the body of the answer.
I think I'm up against a polymorphic association in #Rails, and Jesus Christ, is it ever daunting.
Trying to fetch all answers made by a user for a particular question. Fetching the answers works, fetching the questions works. But I can't seem to do this in a way that question.query and answer.body are displayed together in a coherent fashion.
What I need is to display a question title with a link to the question, then display the body of the answer.
@lnxw48a1 @usrlocalshare When I first learned #ruby I used #ramaze partly because it just wasnt #rails, but also for the ways it wasn't Rails: more minimal, less coupled, etc.
When Rails 3 came out I got a gig working with it, and looking back at Rails 2 I was glad I hadn't had to suffer that epoch. :-)
@usr_local_share Someone once advised me: If you want to learn #Ruby, learn the language first, then you can learn #Rails. $PERSON said #RoR is different enough that if you learn it first, you'll think you know Ruby, but you won't.
I'm writing a StackExchange clone in #Rails today. So far, most of it works, but I am now up against The Dreaded Thing I Suck At, which involves associations.
I've managed to tie Questions to Users, and it works without incident - every Question page will properly represent who asked it. Because this association has been figured out, I can also show every question a particular person has asked. That's good!
Now, I have to figure out how to correctly tie Answers to Questions. Answers are also tied to Users, so I have to be careful about how I hook this together. I've definitely screwed up on this kind of thing before, so I'm taking extra measures to do this work in a separate branch. It's easy to get a little bit too confused and tangle everything up incorrectly.
Once I get the association logic (and controller logic) figured out, I should be able to embed an Answer response form into the show page for questions, and it should Just Work™.
I have an idea for a service that I could likely make with #Rails, and it would spread like wildfire across #Tumblr, if not other places. The only bit of its engineering that I don't really know how to do yet is the saving of historical data about the database's records; I imagine that for my use case it'd involve running a chron job and setting the job up such that it runs through the database, counts all records of a particular type, does so for all types, & saves to other table the counts/typ
Can any #rails folks tell me their opinions on JSON serialization options such as Rabl (we use currently), ActiveModel Serializer, JBuilder and whatever else I may not know about?