cjilbert504

Hey Michael, I'm in the middle of moving at the moment and my new place won't be ready for a little while so I am not able to properly record any videos at the moment. But once I get set back up I can work on the follow up for delete. Unfortunately I don't have any solid estimate of when I will be able to get fully into the new place.

Great stuff!

Hey Aaron, in the video I just used Time.now.to_i initially to show that the fields need a unique value. Yes, re-rendering the fields when validation fails using the Time.now.to_i will cause the fields to all have the same value. It is a problem, but one with a simple fix which is to call task.object_id instead of Time.now.to_i in the app/views/projects/_task.html.erb partial.

Hey Terry - Thanks for the kind words here! And yes, that is a great idea, thank you for sharing that one!

Thanks a bunch, Mateus!

I agree, I'll have to make a short follow up video for that one. Thanks!

First of all, welcome to the Ruby community! I'm super glad to hear that the explanations are helpful for your understanding! Thank you!

Hey Carl - That's a great idea! Thank you

Hey Muhammad,
Sorry that you feel the video is lengthy. At the moment, I do not plan to do a written version and I also don't know that it would be fair to folks that learn better from video to do such a quick video.

Thanks! Glad that you enjoyed it!

Glad to hear that you enjoyed the video! Yeah, I wanted to stay more focused on the overall theme of building utilities so I didn't dive into the regex much, also because it is specific somewhat to my machine. Maybe we could do a little series or a something on Regular Expressions in the future. :)

Thanks! And thanks also for letting us know that you would enjoy more around these topics!

Thank you for the kind words and the feedback! To follow up, initially, the "task_field" endpoint does not automatically return a turbo-stream. In the second implementation when we use the RequestJS package to set a { responseKind: "turbo-stream" } on the request that the Stimulus controller makes, that's what triggers the endpoint to respond with a turbo-stream. Then when we remove the Stimulus controller and solely use Turbo, we set a data: { turbo_stream: true } on the link_to helper, that will also cause the endpoint to respond with a turbo-stream. Although the endpoint is empty during these two implementations, by default if a request comes in that wants a turbo-stream the endpoint can either list out how to respond to a turbo-stream request in the action or by convention look for a matching named turbo-stream view i.e. "app/views/projects/task_field.turbo-stream.erb". This is much like the convention of how a given action, let's say an index action of a Post controller, would look for a view at "app/views/posts/index.html.erb" by default unless instructed otherwise.
Hope this helps clarify that for you!

Thanks for taking the time to provide this feedback. The remaining videos that I have coming out for this year are already recorded but going forward I will be sure to keep this in mind and try to provide an opening overview in the videos. I appreciate the feedback!

Thanks, James! Yeah, progressive enhancement is a good description of it. A bit of a refactoring too as we were able to drop the stimulus controller completely. Happy to hear that you enjoyed the video! Thanks for watching.

Thanks, Matt! I'm glad that you enjoyed this video.

Hey Terry!

Thank you so much for the kind words. I'm glad that you enjoyed the video. I think part 2 will be out next week so hopefully, you enjoy that one as well if you watch it. I definitely agree with you on the core concepts aspect. That was a big motivator for this video.

Hope all is well!

Thanks all for contributing to the conversation! I've added a link to a blog post in the episode notes about this topic and included some things around validating uniqueness.

I'll share what I did today to solve for this, which is really close to what Ryan did. The model, among other attributes, has a title and a rich text description like so:

has_rich_text :description

I wanted to be able to search across both attributes. I had the title one worked out already but to get the rich text description into the mix I then added the following line:

has_one :description, class_name: 'ActionText::RichText', as: :record

Which then allowed me to do this in the form:

f.text_field :title_or_description_body_cont

Hope this adds to the help that was already here and thanks to the other folks who contributed to this thread!!

Now wait a second why didn't you have to use the gem build and gem install commands before including the gem in the gemfile??