« Back to channel list

#RubyOnRails - 20 March 2018

« Back 1 day Forward 1 day »
[00:26:44] madebymarkca: has joined #RubyOnRails
[00:32:54] cagomez: has joined #RubyOnRails
[00:40:38] drewintx: has joined #RubyOnRails
[00:40:59] drewintx: Could anyone possibly help me with an ajax and forms issue?
[00:43:48] SteenJobs: has joined #RubyOnRails
[00:44:53] ulisesqg: has joined #RubyOnRails
[01:08:19] duderonomy: has joined #RubyOnRails
[01:11:48] workmad3: has joined #RubyOnRails
[01:30:53] gravity_pope: has joined #RubyOnRails
[01:43:23] jcarl43: has joined #RubyOnRails
[01:48:21] sevenseacat: has joined #RubyOnRails
[02:06:35] SteenJobs: has joined #RubyOnRails
[02:18:07] saltlake: has joined #RubyOnRails
[02:18:19] saltlake: has left #RubyOnRails: ()
[02:26:58] darkhanb: has joined #RubyOnRails
[02:36:31] duderonomy: has joined #RubyOnRails
[02:38:26] DTZUZO: has joined #RubyOnRails
[02:46:35] xuyuheng: has joined #RubyOnRails
[03:02:33] xall: has joined #RubyOnRails
[03:12:04] workmad3: has joined #RubyOnRails
[03:13:32] orbyt_: has joined #RubyOnRails
[03:32:27] andrewray: has joined #RubyOnRails
[03:36:42] Saukk: has joined #RubyOnRails
[03:44:28] Ropeney: has joined #RubyOnRails
[04:00:20] duderonomy: has joined #RubyOnRails
[04:06:08] quazimodo: has joined #RubyOnRails
[04:25:33] trautwein: has joined #RubyOnRails
[04:33:58] xuyuheng: has joined #RubyOnRails
[04:34:07] za1b1tsu: has joined #RubyOnRails
[04:35:31] ghormoon: has joined #RubyOnRails
[04:36:48] duderonomy: has joined #RubyOnRails
[04:43:12] xuyuheng: has joined #RubyOnRails
[05:06:49] Ropeney: has joined #RubyOnRails
[05:31:36] dionysus69: has joined #RubyOnRails
[05:39:00] duderonomy: has joined #RubyOnRails
[05:49:21] bijan_: has joined #RubyOnRails
[05:49:22] srinidhi: has joined #RubyOnRails
[05:51:43] sidx64: has joined #RubyOnRails
[05:51:55] za1b1tsu: has joined #RubyOnRails
[05:59:00] xuyuheng: has joined #RubyOnRails
[06:03:52] sidx64: has joined #RubyOnRails
[06:10:50] sidx64: has joined #RubyOnRails
[06:14:24] reber: has joined #RubyOnRails
[06:33:33] cschneid: has joined #RubyOnRails
[06:35:34] za1b1tsu: has joined #RubyOnRails
[06:38:43] sidx64: has joined #RubyOnRails
[06:43:17] duderonomy: has joined #RubyOnRails
[06:48:46] halogenandtoast: has joined #RubyOnRails
[06:49:10] halogenandtoast: Does anyone know of a reason that there would be two copies of each asset (with different digests) in public/assets
[06:50:05] halogenandtoast: For example `icon08-small-db168530121b9563b91edf437603be0c.png` and `icon08-small-fbaaba8989a1e343d8ad0393106f5e55.png` both appear
[06:50:09] bijan_: has joined #RubyOnRails
[06:58:39] schneider: has joined #RubyOnRails
[07:00:14] sidx64: has joined #RubyOnRails
[07:05:05] darkhanb: has joined #RubyOnRails
[07:09:49] dminuoso: halogenandtoast: If you clobber and recompile, do you still have both?
[07:10:24] srinidhi: has joined #RubyOnRails
[07:10:27] dminuoso: halogenandtoast: Gist your manifest.
[07:10:53] halogenandtoast: Oh wait, the clobber did work (my os was caching the folding contents for a second)
[07:11:17] dminuoso: ¯\_(ツ)_/¯
[07:11:22] halogenandtoast: Locally it worked, for some reason on my production server, assets:precompile generated two manifest files though
[07:12:12] dminuoso: halogenandtoast: gist your sprockets manifest.
[07:12:34] workmad3: has joined #RubyOnRails
[07:12:48] halogenandtoast: Unfortunately, I can't, this isn't my app (which I know ties hands here)
[07:13:16] dminuoso: halogenandtoast: just look for the information on both assets
[07:13:22] dminuoso: See if they resolve to different paths.
[07:13:32] halogenandtoast: alright will check
[07:13:49] dminuoso: halogenandtoast: You can find the manifest in public/assets/.sprockets....
[07:17:11] halogenandtoast: No such file, might be an older version in use here
[07:17:26] halogenandtoast: I do see files `manifest-5ef964484047092d2672a59e6d513e37.json` and ` manifest-fbb7c6ce0eb69aef71111097dd185313.json` however
[07:18:01] halogenandtoast: sprockets 2.12.4
[07:18:30] halogenandtoast: latest is 3.7.1 so this is quite old
[07:19:12] halogenandtoast: arent clients fun
[07:19:54] sevenseacat: sounds like your next task should be a gem update.
[07:20:21] halogenandtoast: sevenseacat: I'm only here to debug in a read-only context
[07:20:28] halogenandtoast: but that might be my suggestion
[07:21:14] halogenandtoast: rails is 4.2.10 so I'd have to check compatibility
[07:22:00] halogenandtoast: 4.2.10 is at least fairly recent
[07:22:15] conta: has joined #RubyOnRails
[07:22:21] halogenandtoast: comparitively speaking
[07:23:09] sevenseacat: at least it still gets major security fixes (I think).
[07:25:55] DrYockel: has joined #RubyOnRails
[07:31:18] srinidhi: has joined #RubyOnRails
[07:32:56] conta1: has joined #RubyOnRails
[07:33:53] dminuoso: halogenandtoast: Those files then. Check the file for the assets you are seeing.
[07:34:24] dminuoso: Also you might want to hire a consultant if you cant do this on your own.
[07:35:46] sevenseacat: it sounds like they are the consultant
[07:35:59] dminuoso: sevenseacat: So? =)
[07:38:40] ryan_ford: has joined #RubyOnRails
[07:42:42] bijan_: Who sets the Channel Topic? Newest Release is 5.1.5 :D
[07:43:12] sevenseacat: oh hey I can fix that
[07:43:47] sevenseacat: ...once I remember how
[07:44:18] ChanServ: +o sevenseacat
[07:44:39] sevenseacat: ta for that :)
[07:45:18] ChanServ: -o sevenseacat
[07:45:32] bijan_: Ahhhh! Taaadaaa :)
[07:49:07] duderonomy: has joined #RubyOnRails
[07:52:10] sidx64: has joined #RubyOnRails
[07:52:38] mtkd: has joined #RubyOnRails
[07:54:49] halogenandtoast: dminuoso: I'm just support for a PaaS product
[07:55:02] halogenandtoast: Clients do the weirdest things some times and I can't change their files
[07:55:08] halogenandtoast: only try to diagnose
[08:03:06] sidx64: has joined #RubyOnRails
[08:07:59] sidx64: has joined #RubyOnRails
[08:09:33] schneider: has joined #RubyOnRails
[08:16:56] Radar: GOOD EVENING
[08:17:48] schneider: has joined #RubyOnRails
[08:18:49] dminuoso: HELLO RADAR
[08:18:53] dminuoso: CAN YOU FIX MY CODE?
[08:21:52] duderonomy: has joined #RubyOnRails
[08:23:12] jottr: has joined #RubyOnRails
[08:25:54] Radar: dminuoso: It's on line 5
[08:26:08] Radar: You are using a monoid there but really you should be using an endofunctor
[08:27:44] dminuoso: ACTION states matter-of-factly that he's already using an endofunctor
[08:27:53] dminuoso: In fact Im using both!
[08:28:32] dminuoso: The monoid (Array, #+, [])
[08:28:37] dminuoso: As well as the Functor Array
[08:31:42] pfg: has joined #RubyOnRails
[08:31:57] HalcyonicStorm: has joined #RubyOnRails
[08:32:02] mostlybadfly: has joined #RubyOnRails
[08:32:03] LyndsySimon: has joined #RubyOnRails
[08:32:05] ss942: has joined #RubyOnRails
[08:32:05] maciuszek: has joined #RubyOnRails
[08:32:39] ss942: has left #RubyOnRails: ()
[08:33:53] helpa: https://www.leighhalliday.com/best-ruby-and-ruby-on-rails-resources
[08:34:17] sevenseacat: there's also a link to a different resource in the channel topic, but many of the books will be the same.
[08:35:04] sevenseacat: also, I just tried to make bread in the breadmaker by myself for the first time and I'm sure it will turn out awfully.
[08:35:44] Fire-Dragon-DoL: has joined #RubyOnRails
[08:37:41] za1b1tsu: has joined #RubyOnRails
[08:38:27] za1b1tsu: has joined #RubyOnRails
[08:40:29] bijan_: has joined #RubyOnRails
[08:41:14] dminuoso: Is there a way to encode a parameter in such a way, that instead of ids[]=1&ids=[]=2, I could do something like ids[1][f]=bar&ids[2][f]=quux with `ids` remaining an array?
[08:41:29] dminuoso: The documentation on this topic is absolutely horrible.
[08:41:51] elcms: has joined #RubyOnRails
[08:42:04] dminuoso: (i.e. I want to specify the `nth` element of the array)
[08:42:17] sevenseacat: mmmm don't think so
[08:42:32] Radar: !unworthy
[08:42:32] helpa: You are not worthy of this bot!
[08:43:20] Radar: dminuoso: no, you can't do that. Rack::Utils.parse_nested_query I think is the function for that
[08:45:45] dminuoso: Radar: Mmm. That kind of sucks, Im trying to find a clean way to encode paramers for multiple resources (so that it plays nice with strong params). :(
[08:45:57] dminuoso: But that was a helpful hint. Thank.
[08:46:10] Radar: The trick is to not use strong parameters :P
[08:46:24] dminuoso: You are right. to_unsafe_h here we go!
[08:46:53] sevenseacat: I like strong parameters
[08:47:14] sevenseacat: at least, compared to attr_accessible
[08:47:54] dminuoso: sevenseacat: Things that could be done with typ.. ah well.
[08:48:49] sidx64: has joined #RubyOnRails
[08:49:33] dminuoso: Though I could use StrongParameters by hand I guess
[08:49:52] Radar: http://hanamirb.org/guides/actions/parameters
[08:50:04] Radar: ^ I like the whitelisting part here
[08:51:39] Radar: dminuoso: If you want to specify the nth element of the array: chances are you can accept it as a hash and then convert it to an array without fully vomiting everywhere
[08:51:43] sevenseacat: I was about to go 'how does that differ' but I can see that it pushes some validations to the controller layer
[08:52:12] Radar: Where they should be, damn it
[08:53:12] dminuoso: Radar: Ever done an API in a rich type system?
[08:53:40] Radar: dminuoso: nope. I could only dream.
[08:53:51] sevenseacat: graphqlllllllll
[08:54:09] dminuoso: Radar: Servant has this cool thing, where an API is basically just a type specification. So you could do: `type API = "hello" :> QueryParam "name String :> Get '[JSON] HelloMessage`
[08:54:47] dminuoso: So you have a route packed together with exact acceptance criteria for requests - this type flows through your application and prevents incorrect treatment.
[08:55:00] duderonomy: has joined #RubyOnRails
[08:55:54] Radar: dminuoso: WANT.
[08:56:03] Radar: ACTION struggles to think of a job where he hasn't wanted that 
[08:58:59] mikecmpbll: has joined #RubyOnRails
[08:59:35] za1b1tsu: has joined #RubyOnRails
[09:01:09] dminuoso: Radar: It's quite amazing what types are capable of, once you lose the notion that types are just this verbose and useless mess that Java or C++ throws at you.
[09:01:46] dminuoso: Radar: Oh, Servant can of course also generate the appropriate documentation as a cherry ontop! :
[09:02:11] Radar: dminuoso: tbh for documentation I still prefer a human touch
[09:02:57] dminuoso: Radar: It needs a human touch. It's not purely mechanical.
[09:03:24] schneider: has joined #RubyOnRails
[09:03:31] dminuoso: Radar: But the type driven nature makes it really hard for documentation to not match the API specification.
[09:05:09] Radar: Yeah. Those two things getting out of sync can happen fairly often.
[09:07:32] dminuoso: The really cool thing is, that you need to meddle much with the types since inference will have them flow through your application transparently. So you get the benefits of the expressivity, without the annoyance of a gazillion type annotations that slow down writing and reading.
[09:07:41] dminuoso: *that you dont need to!
[09:07:49] dminuoso: Time to break some rails code.
[09:12:10] riotjones: has joined #RubyOnRails
[09:12:48] workmad3: has joined #RubyOnRails
[09:18:01] quazimodo: has joined #RubyOnRails
[09:24:07] rikkipitt: has joined #RubyOnRails
[09:24:32] sidx64: has joined #RubyOnRails
[09:57:44] mtkd: has joined #RubyOnRails
[10:07:31] Fernando-Basso: has joined #RubyOnRails
[10:07:41] xuyuheng: has joined #RubyOnRails
[10:10:43] alfiemax: has joined #RubyOnRails
[10:15:26] alfiemax: has joined #RubyOnRails
[10:15:35] alfiemax: has joined #RubyOnRails
[10:15:53] marr: has joined #RubyOnRails
[10:25:50] lxsameer: has joined #RubyOnRails
[10:39:59] conta: has joined #RubyOnRails
[10:44:14] KeyJoo: has joined #RubyOnRails
[10:46:04] workmad3: has joined #RubyOnRails
[10:49:27] darthShadow: has joined #RubyOnRails
[10:49:31] darthShadow: has left #RubyOnRails: ()
[10:51:15] xuyuheng: has joined #RubyOnRails
[10:52:10] sidx64: has joined #RubyOnRails
[10:55:59] schneider: has joined #RubyOnRails
[11:04:09] ryan_ford: has joined #RubyOnRails
[11:06:18] kapil___: has joined #RubyOnRails
[11:09:27] schneider: has joined #RubyOnRails
[11:15:29] drale2k_: has joined #RubyOnRails
[11:18:56] schneider: has joined #RubyOnRails
[11:19:01] conta: has joined #RubyOnRails
[11:21:45] KeyJoo: has joined #RubyOnRails
[11:26:52] conta: has joined #RubyOnRails
[11:29:35] apparition: has joined #RubyOnRails
[11:33:30] ferr: has joined #RubyOnRails
[11:33:38] ferr: has left #RubyOnRails: ()
[11:38:55] sidx64: has joined #RubyOnRails
[11:43:25] solars: has joined #RubyOnRails
[11:44:04] solars: hey, is anyone using AWS ECS and can tell me how I would separate the database container from my app when using task definitions?
[11:54:02] sidx64: has joined #RubyOnRails
[11:58:40] sidx64: has joined #RubyOnRails
[12:01:57] mtkd: has joined #RubyOnRails
[12:02:16] dionysus69: has joined #RubyOnRails
[12:03:17] cschneid: has joined #RubyOnRails
[12:04:45] apeiros: has joined #RubyOnRails
[12:06:50] sidx64: has joined #RubyOnRails
[12:10:10] xuyuheng: has joined #RubyOnRails
[12:19:01] sidx64: has joined #RubyOnRails
[12:27:04] sidx64: has joined #RubyOnRails
[12:40:05] sidx64: has joined #RubyOnRails
[12:40:46] DrYockel: has joined #RubyOnRails
[12:45:53] lessd: has joined #RubyOnRails
[12:54:08] bijan_: has joined #RubyOnRails
[12:56:35] Ergo: has joined #RubyOnRails
[13:06:14] sidx64: has joined #RubyOnRails
[13:07:28] schneider: has joined #RubyOnRails
[13:11:14] DrYockel: has joined #RubyOnRails
[13:18:09] rikkipitt: has joined #RubyOnRails
[13:28:19] arBmind: has joined #RubyOnRails
[13:29:57] sidx64: has joined #RubyOnRails
[13:37:27] blackcross: how would i make an associate with a model Company and a model Shipment where Shipment would have a ship_from_company and a ship_to_company?
[13:37:57] blackcross: should i use 2 intermediate tables, or has_and_belongs_to_many or what?
[13:38:42] sevenseacat: sounds like a Shipment would belong_to a ship_to_company and a ship_from_company
[13:39:07] sevenseacat: and a Company could have many sent_shipments and received_shipments
[13:48:53] wsmoak: has joined #RubyOnRails
[13:59:43] CGibsonmm: has joined #RubyOnRails
[14:00:28] CGibsonmm: msg NickServ REGISTER cg359997 cgibsonmm@gmail.com
[14:01:01] blackcross: msg nickserv ghost cgibsonmm cg359997
[14:02:51] jottr: has joined #RubyOnRails
[14:04:26] CGibsonmm: okay, anyway I have a question about routing through the a controller, I have an image model that on the create action it renders a crop method to crop a photo, I am looking to do the same thing on the edit method also. so it would route edit crop then update
[14:05:17] LateralOctober: has joined #RubyOnRails
[14:06:34] rikkipitt: I've got a ProjectsController that takes a subset of the Project model fields, that once submittted, takes the user to another controller for adding the remaining fields to Project. I've nested to route, but is this technically not quite restful or should i pretend it is (new/create actions etc)?
[14:06:34] dminuoso: apeiros: time to be brave
[14:06:41] dminuoso: Im gonna try to switch to 2.5
[14:07:50] rikkipitt: as in /project/1/files/new but the underlying model is still the Project
[14:10:33] flujan: has joined #RubyOnRails
[14:11:00] tbuehlmann: dminuoso: how exactly does your cells directory structure look like? do you have one cell per controller action or do you have, like one cell per controller with n methods?
[14:11:40] flujan: hello guys, I have a page which refreshs its contents every 10 seconds. I just performe .get requests using Ajax. The problema is that the tab with this page use as much as 1GB or RAM. When I force reload the page or use window.location.reload if releases all memory.
[14:12:06] rikkipitt: flujan: try action cable instead?
[14:12:10] flujan: I tried to set the http header for no-cache and the headers are all OK, but the memory usage over time keep increasing. Any ideas?
[14:12:32] flujan: rikkipitt: its a legacy app using rails 4.2 and faye for websocket…
[14:12:58] rikkipitt: is it a js memory leak?
[14:13:22] tbuehlmann: flujan: are you somehow keeping the old DOM? how do you update the page contents?
[14:13:34] rikkipitt: try using chrome dev tools to track the memory usage and profile the assignments etc
[14:14:27] flujan: tbuehlmann: .$(‘#DOM’).empty().html(data);
[14:14:28] rikkipitt: this might help get you on your way: https://developers.google.com/web/tools/chrome-devtools/memory-problems/
[14:15:24] dminuoso: tbuehlmann: On average I have maybe 3-5 cells per action
[14:15:50] dminuoso: tbuehlmann: But that's just statistics. In reality they are controller agnostic as much as possible (apart from some outer "index" cells), and rather feature centric.
[14:15:59] dminuoso: (Trying to promote reusability as much as possible)
[14:16:57] tbuehlmann: let's assume we have a TasksController with regular CRUD actions. how does your directory for its cells look like? or do you adopt trailblazer's concepts style?
[14:17:07] flujan: rikkipitt: thanks
[14:17:23] rikkipitt: flujan: no worries
[14:17:28] flujan: I am already uing it… it is the js heap that keep growing.
[14:17:33] tbuehlmann: I'm thinking about having only one method (#show) per cell vs having several methods per cell (#index, #show, #new, …)
[14:17:55] dminuoso: tbuehlmann: Oh absolutely.
[14:18:09] rikkipitt: flujan: put the ajax up so we can see it, might be able to spot any glaring issues
[14:18:10] dminuoso: tbuehlmann: You're not supposed to have multiple show methods really.
[14:18:22] dminuoso: tbuehlmann: (I mean you can do it, but that takes you away from all the goodieS)
[14:18:47] dminuoso: tbuehlmann: How do you like them so far?
[14:18:56] tbuehlmann: right. that's what https://github.com/trailblazer/cells somehow suggests
[14:19:12] tbuehlmann: trying to get warm with it, but it's not too easy since documentation isn't clear
[14:19:30] tbuehlmann: also the distinction between cells, trailblazer-cells and rails-cells wasn't clear at first
[14:19:39] tbuehlmann: now it's really just about structuring cells for me
[14:20:05] dminuoso: tbuehlmann: I think there is no golden recipe. Use what fits your application best.
[14:20:11] tbuehlmann: yeah, I guess
[14:22:55] dminuoso: tbuehlmann: There's nothing really wrong with mimicing rails layout should you want this though. It's not bad per se.
[14:23:02] gravity_pope: has joined #RubyOnRails
[14:25:44] DTZUZO: has joined #RubyOnRails
[14:27:20] tbuehlmann: cells-rails urges me to use several methods per cell, which I don't like. so then there's trailblazer-cells which has the right folder structure but missing cells-rails's goodies
[14:28:39] dminuoso: tbuehlmann: how does cells-rails urge you to?
[14:29:27] dminuoso: tbuehlmann: all cells-rails does really, is provide some helpers and thats it
[14:29:34] dminuoso: (and some other minor things)
[14:30:58] dminuoso: tbuehlmann: I dont use trailblazers-cells because I couldnt make it work with my setup - too many autoloading problems after which I just went for pure cells/cells-rails
[14:31:30] tbuehlmann: I'd have to search for that unclear documentation but I'm too confused right now
[14:31:49] dminuoso: tbuehlmann: there may be instances where you want some extra view logic, but dont want a full fleged cell - I sometimes do this with inline methods producing strings, sometimes I render extra templates
[14:32:10] dminuoso: let me give you a particularly ugly example Im working on right now
[14:35:00] kn-928: has joined #RubyOnRails
[14:35:10] dminuoso: And boy am I not proud of this.
[14:36:44] tbuehlmann: will have to think more about the structure I'd prefer
[15:02:57] MacWinner: has joined #RubyOnRails
[15:03:04] Jon30: has joined #RubyOnRails
[15:04:22] catbusters: has joined #RubyOnRails
[15:07:14] mtkd: has joined #RubyOnRails
[15:24:39] Dimik: has joined #RubyOnRails
[15:25:43] troys: has joined #RubyOnRails
[15:37:30] mikecmpb_: has joined #RubyOnRails
[15:45:11] jcarl43: has joined #RubyOnRails
[15:48:43] one_zero: has joined #RubyOnRails
[15:54:29] cagomez: has joined #RubyOnRails
[16:00:47] lessd: has joined #RubyOnRails
[16:04:28] [Butch]: has joined #RubyOnRails
[16:06:23] srinidhi: has joined #RubyOnRails
[16:07:09] za1b1tsu: has joined #RubyOnRails
[16:07:25] gravity_pope: has joined #RubyOnRails
[16:17:37] mikecmpbll: has joined #RubyOnRails
[16:20:25] FrostCandy: has joined #RubyOnRails
[16:20:33] desperek: has joined #RubyOnRails
[16:22:44] FrostCandy: Anyone know why my gem would work on my local system but not on my production server? I'm new to ruby so probably something easy. when i do GEM LIST i get zeroclipboard-rails (0.1.2) but in my Gemfile it shows gem 'zeroclipboard-rails', '~> 0.1.0' , is that a problem?
[16:24:30] duderonomy: has joined #RubyOnRails
[16:26:34] SteenJobs: has joined #RubyOnRails
[16:32:10] fryguy: those match so that's not a problem
[16:32:16] fryguy: what does "doesn't work" mean here
[16:33:03] CGibsonmm: has joined #RubyOnRails
[16:33:14] CGibsonmm: having issue with my cropper.js file called form a gem being rendered too soon and default styles and fucntion not working unless reloading the page. Is there an easy way to hold up the render?
[16:33:29] dminuoso: FrostCandy: You might be interested in giving this a brief read: http://bundler.io/v1.5/gemfile.html
[16:33:50] CGibsonmm: will check it out
[16:35:53] schneider: has joined #RubyOnRails
[16:47:03] darkhanb: has joined #RubyOnRails
[16:49:17] za1b1tsu: has joined #RubyOnRails
[16:50:48] CGibsonmm: has left #RubyOnRails: ()
[16:51:18] FrostCandy: fryguy: so minor versions match? ok. If I got to my production server, where would you go to get a gem list ? Do I just have to figure out where ruby is installed on the amazon webserver then run the command GEM LIST there? - also thanks dmi i'll read it now.
[16:54:09] FrostCandy: fryguy: ah ok ~> greater than or equal to
[16:55:07] dminuoso: FrostCandy: No.
[16:55:13] FrostCandy: well major version
[16:55:18] FrostCandy: 2 - 2.9999999
[16:55:42] dminuoso: FrostCandy: Right.
[16:56:10] FrostCandy: 2.0.1 - 2.0.9999 actually lol
[16:56:27] FrostCandy: still have a problem though - maybe after i finish reading your doc i'll figure it out.
[16:58:35] FrostCandy: fryguy: to answer your question - dosen't work means on my test server i can click a button that autoamtically copy's the text of a textara box - but on my production server nothing happens when i click the ZeronClip button
[16:58:54] dminuoso: FrostCandy: Again no.
[16:58:55] FrostCandy: made me think there was a gem discrepency
[16:59:18] dminuoso: FrostCandy: `~> 2.0.1` is equal to `>= 2.0.1 && < 2.1`
[16:59:57] dminuoso: FrostCandy: ~> means: any minor/micro/etc upgrade allowed.
[17:00:47] FrostCandy: oh yup i see it now misread their exmaple
[17:08:24] FrostCandy: ok the zeroclipboard-rails (0.1.2) is on my prod server too, must be something else causeint it to work on test server but not on prodution
[17:11:58] mtkd: has joined #RubyOnRails
[17:14:58] Saukk: has joined #RubyOnRails
[17:26:28] mtkd: has joined #RubyOnRails
[17:31:35] lunarkitty7: has joined #RubyOnRails
[17:42:29] FrostCandy: So - one site was blocking flash , the other was not :) Derp.
[17:42:49] FrostCandy: Chrome wasn't reporting that it was blocking the flash plugin though which was wierd so it took me a while to figure it out .
[17:42:59] rikkipitt: does anyone know how to attach a has_many_attached file in factory_bot?
[17:43:03] rikkipitt: factory_bot/activestorage
[17:45:26] uksio: has joined #RubyOnRails
[17:56:15] dionysus69: has joined #RubyOnRails
[17:59:36] gravity_pope: has joined #RubyOnRails
[18:00:49] conta: has joined #RubyOnRails
[18:04:10] jottr: has joined #RubyOnRails
[18:04:34] gravity_pope: has joined #RubyOnRails
[18:24:18] jottr: has joined #RubyOnRails
[18:25:05] mikecmpbll: has joined #RubyOnRails
[18:35:32] srinidhi: has joined #RubyOnRails
[18:51:45] Cavallari: has joined #RubyOnRails
[18:59:44] SteenJobs: has joined #RubyOnRails
[19:08:36] krawchyk: has joined #RubyOnRails
[19:11:00] gravity_pope: has joined #RubyOnRails
[19:23:45] Ryzokuken: has joined #RubyOnRails
[19:26:48] za1b1tsu: has joined #RubyOnRails
[19:28:59] conta1: has joined #RubyOnRails
[19:30:59] mtkd: has joined #RubyOnRails
[19:35:54] cagomez: has joined #RubyOnRails
[19:36:56] za1b1tsu: has joined #RubyOnRails
[19:41:41] duderonomy: has joined #RubyOnRails
[19:53:04] za1b1tsu: has joined #RubyOnRails
[20:16:37] sameerynho: has joined #RubyOnRails
[20:41:11] cagomez: has joined #RubyOnRails
[20:43:21] duderonomy: has joined #RubyOnRails
[21:00:33] elcms: has joined #RubyOnRails
[21:09:46] workmad3: has joined #RubyOnRails
[21:14:45] DrYockel: has joined #RubyOnRails
[21:15:42] gravity_pope: has joined #RubyOnRails
[21:18:28] quazimodo: has joined #RubyOnRails
[21:34:50] Radar: GOOD MORNING
[21:36:05] mtkd: has joined #RubyOnRails
[21:37:53] dminuoso: On that note: good night
[21:52:58] schneider: has joined #RubyOnRails
[21:56:06] SanguineAnomaly: has joined #RubyOnRails
[22:03:31] conceivably: has joined #RubyOnRails
[22:06:21] conceivably: Hello :) Possibly a silly question, I'd like to avoid shooting myself in the foot, but is there any reason as to why it would be a bad idea to have one model inherit from another with both sharing the same database table? I have an optional association, and depending on whether or not it exists I want to add some additional functionality. Or is there a better, canonical way of dealing with this situation?
[22:11:18] SanguineAnomaly: conceivably, that sounds like fairly standard single table inheritance so I'd guess it's fine (although it's a long time since I ever had to do something like that, so maybe times have changed :/)
[22:14:27] moei: has joined #RubyOnRails
[22:15:34] conceivably: Sort of, I guess, just that I don't have a type column. Hmm...but perhaps I should have one.
[22:30:35] zacts: has joined #RubyOnRails
[22:32:18] workmad3: has joined #RubyOnRails
[22:38:18] schneider: has joined #RubyOnRails
[22:47:49] kn-928: has joined #RubyOnRails
[22:53:48] Radar: conceivably: what are the two models involved?
[22:53:53] Radar: What are their purposes?
[23:03:08] greengriminal: has joined #RubyOnRails
[23:05:02] xall: has joined #RubyOnRails
[23:08:59] cagomez: has joined #RubyOnRails
[23:20:18] schneider: has joined #RubyOnRails
[23:27:01] kn-928: has joined #RubyOnRails
[23:38:18] kapil___: has joined #RubyOnRails
[23:41:43] ule: has joined #RubyOnRails
[23:47:32] kn-928: has joined #RubyOnRails
[23:56:54] mroutis: has joined #RubyOnRails