twilling

Activity Graph

Page 1 of 5 | Next »

2018-05-17

[02:32:43] twilling: has joined #RubyOnRails
[03:37:08] twilling: Quit: twilling
[03:42:17] twilling: has joined #RubyOnRails
[03:57:32] twilling: Quit: twilling

2018-04-22

[03:57:58] twilling: has joined #RubyOnRails
[04:02:46] twilling: I’m currently working on an app that has articles written in markdown (and parsed via redcarpet). I would like to give authors the ability to add a “tag” to indicate where ads should be placed. I could probably do something in plain ruby but I’m wondering if there are gems anyone has used for a similar purpose (parsing portions of markup)
[04:03:38] twilling: Quit: twilling
[04:14:01] twilling: has joined #RubyOnRails
[04:14:13] twilling: damnit… closed my laptop without thinking so i don’t know if anyone responded to my earlier message
[04:26:05] twilling: Quit: twilling
[04:26:33] twilling: has joined #RubyOnRails
[05:49:08] twilling: Quit: twilling
[05:56:25] twilling: has joined #RubyOnRails
[06:03:19] twilling: Quit: twilling
[06:11:05] twilling: has joined #RubyOnRails
[06:22:10] twilling: Quit: twilling
[08:02:03] twilling: has joined #RubyOnRails
[08:24:17] twilling: Ping timeout: 268 seconds
[08:28:12] twilling: has joined #RubyOnRails
[08:32:43] twilling: Ping timeout: 265 seconds

2018-03-04

[21:55:19] twilling: has joined #RubyOnRails
[21:55:22] twilling: Client Quit

2018-03-03

[01:30:26] twilling: Quit: twilling
[01:34:21] twilling: has joined #RubyOnRails
[02:09:45] twilling: Quit: twilling
[21:20:59] twilling: has joined #RubyOnRails
[21:59:04] twilling: Quit: twilling
[22:03:45] twilling: has joined #RubyOnRails
[22:29:32] twilling: Quit: twilling

2018-03-02

[18:26:32] twilling: has joined #RubyOnRails

2018-03-01

[02:12:40] twilling: has joined #RubyOnRails
[02:53:59] twilling: Quit: twilling
[16:27:00] twilling: has joined #RubyOnRails
[16:34:10] twilling: Quit: twilling

2017-12-14

[01:56:47] twilling: has joined #RubyOnRails
[03:31:51] twilling: Quit: twilling

2017-11-07

[00:01:38] twilling: has joined #RubyOnRails
[00:02:22] twilling: I have the following in my controller and `find_by!` isn’t raising an exception for me. This is weird, right? `Article.published.find_by!(slug: params[:slug])`
[00:02:50] twilling: (This is in a Rails 5.1.2 app)
[00:08:58] twilling: I get errors in the view because I’m calling methods on nil, but the entire contents of this `show` method is `@article = Article.published.find_by!(slug: params[:slug])` it’s weird
[00:41:06] twilling: Quit: twilling
[15:00:26] twilling: has joined #RubyOnRails
[15:01:23] twilling: Client Quit
[15:30:51] twilling: has joined #RubyOnRails
[22:44:29] twilling: has left #RubyOnRails: ()

2017-09-30

[17:52:09] twilling: has joined #RubyOnRails
[18:00:56] twilling: Quit: twilling
[22:27:49] twilling: has joined #RubyOnRails
[22:58:11] twilling: Quit: twilling
[23:37:06] twilling: has joined #RubyOnRails
[23:37:43] twilling: Client Quit
[23:38:36] twilling: has joined #RubyOnRails
[23:57:02] twilling: Quit: twilling

2017-09-29

[02:32:15] twilling: has joined #RubyOnRails
[03:30:29] twilling: Quit: twilling
[14:22:06] twilling: has joined #RubyOnRails
[14:40:56] twilling: Quit: twilling

2017-09-12

[00:01:36] twilling: has joined #RubyOnRails
[00:09:39] twilling: Quit: twilling
[22:19:55] twilling: has joined #RubyOnRails
[23:18:33] twilling: Quit: twilling

2017-09-11

[18:07:25] twilling: has joined #RubyOnRails
[18:21:44] twilling: Quit: twilling
[22:40:12] twilling: Client Quit
[22:40:12] twilling: has joined #RubyOnRails
[22:40:56] twilling: has joined #RubyOnRails
[22:41:08] twilling: Client Quit
[22:41:40] twilling: has joined #RubyOnRails
[22:42:04] twilling: Client Quit
[22:42:33] twilling: has joined #RubyOnRails
[22:43:00] twilling: Client Quit
[22:43:33] twilling: has joined #RubyOnRails
[22:43:56] twilling: Client Quit
[22:45:14] twilling: has joined #RubyOnRails
[23:17:36] twilling: Quit: twilling
[23:19:47] twilling: has joined #RubyOnRails
[23:26:10] twilling: Quit: twilling

2017-09-08

[02:54:02] twilling: Quit: twilling

2017-09-07

[01:24:22] twilling: has joined #RubyOnRails
[02:27:05] twilling: Quit: twilling
[22:32:28] twilling: has joined #RubyOnRails

2017-09-01

[08:01:50] twilling: has joined #RubyOnRails
[08:06:23] twilling: Ping timeout: 248 seconds
[12:50:54] twilling: has joined #RubyOnRails
[12:51:04] twilling: Client Quit

2017-08-29

[01:46:52] twilling: has joined #RubyOnRails
[01:50:46] twilling: Client Quit
[02:33:56] twilling: has joined #RubyOnRails
[02:35:26] twilling: Client Quit
[02:35:46] twilling: has joined #RubyOnRails
[03:41:00] twilling: Quit: twilling
[21:34:27] twilling: has joined #RubyOnRails
[22:12:26] twilling: Quit: twilling

2017-08-28

[00:52:03] twilling: has joined #RubyOnRails
[00:56:09] twilling: If I have a Post which `has_many :categories, through: :post_categories` (habtm + join model), I know that I can do `Post.joins(:categories).where(categories: { slug: ['cat-a', 'cat-b'] })` and fetch the Posts which belong to either category.
[00:56:10] twilling: However, I want to be able to get Posts assigned to BOTH categories, not either or. Can I get some guidance on the best way to approach this?
[01:07:22] twilling: @Ropeney do you know of a way to do that through ActiveRecord a little more directly rather than building up a string?
[02:37:29] twilling: Quit: twilling
[02:47:17] twilling: has joined #RubyOnRails
[02:50:21] twilling: Ropeney: what would you suggest if there’s not a fixed limit to the number of combinations I can have?
[02:51:37] twilling: Sorry this is about my earlier joins/multiple where question earlier. The intention is to let users pick any number of combinations of categories for filtering posts down. So while my example talks about cat-a and cat-b as being slugs to query for Posts associated with, there could also be 3 other slugs provided. Or any number of slugs
[02:55:04] twilling: Any easier design in terms of the posts to categories relationship?
[02:57:15] twilling: I can have an infinite number of categories using slugs
[02:58:36] twilling: oh, sorry. i’ve explained something wrong…
[02:58:57] twilling: i will draft up a quick gist...
[03:02:49] twilling: this is kind of what i’m after
[03:02:50] twilling: https://gist.github.com/anonymous/a15abf10e6ee0e4e8b36d5d71ca14f34
[03:05:39] twilling: you mean like this, Ropeney? https://gist.github.com/anonymous/80287c200c903b725753e7d4b93e3871
[03:07:55] twilling: ha no worries, i appreciate that :)
[03:08:19] twilling: 1 Subquery for every category whose slug I need to check?
[03:09:56] twilling: it might just be that it’s late. just taking a little while to imagine this
[03:14:04] twilling: @Radar that’s correct
[03:14:26] twilling: @matthewd parsing :)
[03:27:50] twilling: @matthewd so like, EXISTS … AND EXISTS … AND EXISTS … for however many category slugs I need to filter by?
[03:31:12] twilling: im ok with sacrificing a little performance for maintainbility
[03:31:18] twilling: but i don’t know how to do that with activerecord :p
[04:04:28] twilling: i did something that i’m not sure i love with activerecord
[04:08:43] twilling: https://gist.github.com/anonymous/010edfbb0e41372e3a2db6414daa71ba
[04:11:42] twilling: i think once things are named appropriately/extracted it will be more readable
[04:19:45] twilling: i would post the query plan but i’ve made up the scenario to post here so i’m not showing my actual code :p
[04:19:50] twilling: and that’s a lot of finding and replacing...
[04:20:23] twilling: it is using IN instead of EXISTS
[04:22:38] twilling: i find/replaced anyway
[04:23:03] twilling: it may not be 100% but https://gist.github.com/anonymous/d15d8bf078682c326671ed17827a874c
[04:23:26] twilling: that would be doing something like Post.with_all_categories([‘cat-a’, ‘cat-b’])
[04:55:04] twilling: Quit: twilling
[22:41:51] twilling: has joined #RubyOnRails
[23:15:20] twilling: Quit: twilling

2017-07-21

[02:36:08] twilling: has joined #RubyOnRails
[03:00:55] twilling: Quit: twilling
[03:22:43] twilling: has joined #RubyOnRails
[04:22:44] twilling: Quit: twilling

2017-07-20

[01:15:57] twilling: has joined #RubyOnRails
[01:28:52] twilling: Quit: twilling
[02:23:22] twilling: has joined #RubyOnRails
[03:36:01] twilling: Quit: twilling
[22:36:27] twilling: has joined #RubyOnRails
[23:15:35] twilling: Quit: twilling

2017-07-13

[01:04:39] twilling: has joined #RubyOnRails
[03:24:22] twilling: Quit: twilling
[18:42:57] twilling: has joined #RubyOnRails
[19:36:10] twilling: Quit: twilling
[20:33:35] twilling: has joined #RubyOnRails
[20:38:57] twilling: Quit: twilling

2017-07-09

[20:06:25] twilling: has joined #RubyOnRails
[20:19:03] twilling: Quit: twilling
[20:23:10] twilling: has joined #RubyOnRails
[20:24:16] twilling: Client Quit

2017-07-07

[00:32:38] twilling: has joined #RubyOnRails
[00:58:59] twilling: Quit: twilling
[02:20:58] twilling: has joined #RubyOnRails
[02:35:26] twilling: Quit: twilling

2017-07-06

[02:06:55] twilling: has joined #RubyOnRails
[03:10:16] twilling: Quit: twilling
[22:32:24] twilling: has joined #RubyOnRails
[23:20:40] twilling: Quit: twilling

2017-06-22

[14:11:33] twilling: has joined #RubyOnRails
[14:42:53] twilling: Quit: twilling

2016-07-16

[00:22:18] twilling: Quit: twilling
[00:40:04] twilling: has joined #RubyOnRails
[01:11:18] twilling: Quit: twilling
[01:12:50] twilling: has joined #RubyOnRails
[01:13:48] twilling: Client Quit
[14:55:34] twilling: has joined #RubyOnRails
[15:01:06] twilling: Quit: twilling

2016-07-15

[01:27:03] twilling: has joined #RubyOnRails
[02:15:04] twilling: Quit: twilling
[02:39:03] twilling: has joined #RubyOnRails
[03:20:10] twilling: Quit: twilling
[03:55:15] twilling: has joined #RubyOnRails
[03:58:09] twilling: Client Quit
[22:42:17] twilling: has joined #RubyOnRails
[22:45:06] twilling: Client Quit
[22:51:06] twilling: has joined #RubyOnRails

2016-07-14

[02:42:30] twilling: has joined #RubyOnRails
[03:03:15] twilling: Quit: twilling
[03:03:38] twilling: has joined #RubyOnRails
[03:15:49] twilling: Quit: twilling
[23:25:10] twilling: has joined #RubyOnRails
[23:51:12] twilling: Quit: twilling

2016-06-14

[00:03:10] twilling: Quit: twilling
[00:23:29] twilling: has joined #RubyOnRails
[00:50:38] twilling: Quit: twilling
[01:00:49] twilling: has joined #RubyOnRails
[01:11:02] twilling: Quit: twilling
[01:47:55] twilling: has joined #RubyOnRails
[02:27:06] twilling: Quit: twilling
[02:31:08] twilling: has joined #RubyOnRails
[02:38:59] twilling: Quit: twilling

2016-06-13

[23:34:15] twilling: has joined #RubyOnRails

2016-06-02

[01:32:25] twilling: has joined #RubyOnRails
[03:06:10] twilling: Quit: twilling

2016-05-12

[02:30:49] twilling: has joined #RubyOnRails
[03:41:12] twilling: Quit: twilling
[23:12:39] twilling: has joined #RubyOnRails
[23:17:55] twilling: Quit: twilling

2016-05-11

[00:54:01] twilling: Quit: twilling
[00:54:25] twilling: has joined #RubyOnRails
[01:03:03] twilling: Quit: twilling

2016-05-10

[00:19:55] twilling: Quit: twilling
[00:26:48] twilling: has joined #RubyOnRails
[04:01:38] twilling: Quit: twilling
[23:15:51] twilling: has joined #RubyOnRails

2016-05-09

[00:42:23] twilling: has joined #RubyOnRails
[02:58:37] twilling: Quit: twilling
[03:09:27] twilling: has joined #RubyOnRails
[03:10:47] twilling: Client Quit
[23:48:37] twilling: has joined #RubyOnRails

2016-05-08

[18:21:57] twilling: has joined #RubyOnRails
[18:22:22] twilling: does anyone here use thoughtbot’s shoulda matchers?
[18:25:46] twilling: I don’t have an issue. I’m just interested in whether people often use the valdiation matchers or the association matchers for instance. I see their use during TDD but I can also see the argument for removing them after the design is set (because I should trust the Rails api right?)
[18:27:30] twilling: shoulda-matchers provides matchers for specific validations - i.e. `validate_presence_of`
[18:36:15] twilling: Build an app that you want. Maybe it’s just something to keep track of your weekly stuff interests, todos, etc. But make something that keeps you motivated to work on it since you’re the beneficiary but also use it as a playground for showing off your abilities. Liking integrating with websockets, or pushing work off to a job queue etc
[18:38:10] twilling: DaniG2k: have you asked for criticism on those apps?
[18:39:34] twilling: DaniG2k: are you giving them access to the source?
[20:16:16] twilling: Quit: twilling
[21:22:42] twilling: has joined #RubyOnRails
[22:36:07] twilling: Quit: twilling

2016-04-27

[00:13:30] twilling: has joined #RubyOnRails
[00:56:23] twilling: Quit: twilling
[00:56:44] twilling: Client Quit
[00:56:44] twilling: has joined #RubyOnRails

2016-04-26

[03:12:44] twilling: Quit: twilling
[03:13:19] twilling: has joined #RubyOnRails
[03:14:18] twilling: Client Quit
[22:49:00] twilling: has joined #RubyOnRails
[23:19:00] twilling: Quit: twilling

2016-04-25

[02:42:04] twilling: Quit: twilling
[03:11:47] twilling: has joined #RubyOnRails
[03:47:59] twilling: Quit: twilling
[22:40:38] twilling: has joined #RubyOnRails

2016-04-24

[01:08:30] twilling: There’s a contract but there’s nothing binding the concepts
[01:10:32] twilling: domgetter: there are ways you can tie these things together. i just want to strongly advise you against doing it. i’ve seen these ideas, which are well intentioned, because very confusing and unmaintainable with age and/or scale
[01:10:55] twilling: because should be “become"
[01:18:26] twilling: got action cable working, didn’t see anything anywhere before about mounting the ActionCable server. facepalm
[01:40:47] twilling: Radar: you got me :)
[03:52:21] twilling: shibly: http://stackoverflow.com/questions/13530042/execjsruntimeerror-in-usersindex-ror
[04:00:01] twilling: Is `therubyracer` still commented out in your gemfile?
[04:01:08] twilling: uncomment, install, try again
[04:04:40] twilling: http://bundler.io/v1.5/bundle_platform.html
[04:05:18] twilling: do you have node installed locally?
[14:23:28] twilling: How can I determine when a channel should stream? I have a ConversationChannel that I want to stream only when a particular conversations#show page has rendered (because I’ve have been able to determine if someone has acccess at that point).
[14:33:15] twilling: What is the current best resource for learning about ActionCable?
[15:07:29] twilling: mustmodify: I’m reading rails/rails/tree/master/actioncable on github right now
[15:07:39] twilling: mustmodify: do you have experience with it?
[15:40:03] twilling: Quit: twilling
[16:16:12] twilling: has joined #RubyOnRails
[19:23:18] twilling: Quit: twilling
[22:09:16] twilling: has joined #RubyOnRails