kobaltz

635114?v=3&s=250

Joined 7/18/2015
# Name
635114?v=3&s=64
kobaltz said 2 months ago:

Their later versions should support Turbolinks and Rails 5. However, they did deprecate the Uniqueness validation as it could be seen as a security risk. You shouldn't have to specify the branch anymore.

Photo
Denny Deng said 2 months ago:

gem 'client_side_validations'

I tried to bundle install this and worked.

With so many trial and errors, I still could not figure this out. 

Photo
Denny Deng said 2 months ago:

It is working now after I have restarted the server!


Thank you  so much!

635114?v=3&s=64
kobaltz said 2 months ago:

Great! Glad to hear!

635114?v=3&s=64
kobaltz said 2 months ago:

Great! Glad to hear!

635114?v=3&s=64
kobaltz said about 2 months ago:

Sounds interesting. I'll put this on my list of episodes to cover.

At a first glance, I would approach it a few different ways:

1. use sidekiq-cron and create a scheduled task to monitor all of the "notifications" that need to be sent out. Downfall is that as the application grows, even a well indexed table could start to get slow to query.

2. use sidekiq to tie into activejob's perform at. With sidekiq it would look something like this

Job.set(wait_until: send_at_this_time).perform_later(something)

And the benefit of this approach would be that the query wouldn't need to happen since the job is already queued to execute at a later time. The downfall of this could be an improperly configured Redis instance (memory set to volatile instead of nonvolatile) which could result in missing jobs.

If data integrity was an must, I typically prefer persistent queues like delayed_job over in memory. However, this is questionable on "data integrity", but it makes me feel better inside that critical data is not lost in a memory/persistent (write cache to disk) queue.


Regardless, I think option 2 would be a better way to go, there would just have to be some sort of hook to remove the job if the scheduled event were cancelled.

635114?v=3&s=64
kobaltz said about 2 months ago:

Thanks for the heads up. I've updated the show notes.

635114?v=3&s=64
kobaltz said about 2 months ago:

The terminal command I used was

tail -f log/development.log

I recently wrote a blog post about Tail and Grep. https://blog.driftingruby.com/a-tail-of-debugging-issues/

635114?v=3&s=64
kobaltz said about 1 month ago:

Absolutely. However, I was illustrating the point of how the different classes would act. However, since the Emergency and Friend inherit from Contact, any common duplication would best live in Contact.

635114?v=3&s=64
kobaltz said 15 days ago:

It could be an issue on the onImageUpload callback in the summernote initialization. Basically, this callback will listen for image uploads and in the example, we're calling a separate javascript function (sendFile). The sendFile function will make an AJAX post to your application at a different endpoint and will handle the uploading to S3. The success callback of this AJAX request should return a hash with the URL of the S3 image. The success callback will create the image element with the URL from the returned hash and that will be what gets inserted.

635114?v=3&s=64
kobaltz said 13 days ago:

Thank you! It has been a long time coming.

635114?v=3&s=64
kobaltz said 6 days ago:

Agreed, will be covering both of those in upcoming episodes.

635114?v=3&s=64
kobaltz said 4 days ago:

Hello. I plan on continuing the series with other parts of testing; Capybara, FactoryGirl, Mock, CI, CD, etc.