Page 1 of 15 | Next »
[22:19:13] choke: i've got a small issue in production and i'm not sure what the actual problem is. if i run `rails s` within production, i'm getting `Mail is not a module` error, but nowhere in my code have I defined Mail as a module. https://gist.github.com/jblac/7e9d341882e825252eb7c0b78c8fcf9a is a link to the gist, any assistance provided is greatly appreciated.
[22:32:41] choke: @havenwood I do not, in fact the only models I have that start with m is message, message_observer, message_template and metric. This pull request also introduces a mail_helper within the helpers, which does make reference to SendGrid::Mail.new
[22:36:38] choke: I actually have done an include SendGrid -- i wonder if i remove that, if the sendgrid will still work (i forget why I added it). as is, i can't even `rails c` from within the directory
[22:39:05] choke: i removed the include and i can indeed get it started... just clarifying more, I also have `require 'sendgrid-ruby'`, `require 'json'` and `include UrlHelper`. - any of those have customary no-nos attached to them that you're aware of?
[18:37:51] choke: seems weird as i'm passing post parameters or the request object around everywhere. thoughts?
[18:37:51] choke: I am building an API, I have some a post body that contains some fields that are there solely for determining if i should send an email or not, so, what's the best way to handle that? making them attributes on the model seems off since they only apply for this decision, sending the mail from the controller while would work - seems like i'm adding too much logic to the controller, and adding everything to a series of helpers also
[19:49:40] choke: using https://github.com/rails/rails-observers is there any way to make the context used to save available to the observer?
[21:48:15] choke: Hey all, having a small routing problem with Rails5. Hoping I can get some insight. I've outlined everything at https://gist.github.com/jblac/14e1493aae25cbb1800356170677723b but if there are any other questions, please do ask.
[04:16:53] choke: documentation for my user_type_a routes, user_type_b routes, and one that's all inclusive )... I'm either an idiot and all these gems are great, i'm trying to do something I shouldn't, or documenting is seriously the worst job ever... Not sure how to get this done quickly and easily -- any insight?
[04:16:53] choke: Hey all i'm trying to document my api and i'm having issues... major issues... Been dealing with this for a week with nothing to show for it... started off with swagger-docs gem and of course it's out of date... moved to swagger-blocks gem, has really bad documentation... moved to rswag gem, no-go... checked out apipie - couldn't figure out how to have different versions AND different subsets ( i need a separate set of
[04:21:30] choke: hey all, i have a quick question regarding creating documentation... I have a full-featured API of a monolith web application and I'm working on docs currently. Are there any tools to generate different types of documentation?
[04:21:38] choke: What I mean is I have different user-types ( companies, internal, vendors, etc ) so I want to provide a docs link that provides information only on the items available for a specific user type -- not sure if its possible or if i should even worry about it.
[04:30:42] choke: I'll look at it -- I was generating swagger-blocks which is good ( kinda ) but as far as I can tell doesn't have the ability to be selective about what gets generated it's an all-or-nothing sort of thing.
[04:31:13] choke: Never had to do docs before ( at least official docs ) all api's i've done have been private api's for use by a web/mobile system.
[06:37:14] choke: ^ Agreed, though if you wanted to do it in ruby -- you could maybe use the gem list functionality somehow ie: gem list -i "^gem_name$"
[06:37:43] choke: I know that with mysql2 without certain libraries installed, it won't let you install the gem -- so it'd be one way to tell if pg is installed if the gem acts the same way.
[06:39:16] choke: I'm currently having all sorts of problems with it ( not really, it's mostly problems trying to bring a horribly designed php application that's in production to rails, without being able to modify the database up-front to make it rails friendly )
[06:41:10] choke: 'cause, the php application will remain in place -- and the rails app is a json api, that i'll eventually migrate the php side to utilize ( I'm the only ruby dev on the team, everyone else is only php so I can't just bring the entire app to ruby )
[06:46:59] choke: One guy is learning ruby to help me out ( because my task list is about 3 years worth of work )... But the others - not so much. I pick my battle on this one...
[06:47:28] choke: Once the api is done, we're in a position that we can change the look and even the language multiple times a year and the functionality will always be the same.
[06:48:54] choke: Of course, so far - in 3 months of working on this myself, i've got over 3000 tests ( a bunch of pundit spec, and a bunch of request and unit spec )