cjilbert504

Hey Eric! Thanks for checking out the course and sorry for the issue you had getting the app running though I'm glad to hear that you were able to get past it. If you wish to follow along with the videos and code on the app yourself you'll want to checkout the first commit in the repository locally so that your app will be at the starting point of the project as opposed to the finished app. You can do that by running git checkout d966d4f.

I've also updated the README on the rails repository for the course to reflect running the needed database step, thanks for writing in about this one!

Thanks, Peter! Very good to know. I've updated the code to use a mutation observer which is what they have been deprecated in favor of instead. The code for the Stimulus controller has been updated on the repo but I'm going to add it here as well for anyone coming to this video:

export default class extends Controller {
  static targets = [ "messages", "textArea" ]

  connect() {
    this.setScrollPosition();
    this.observer = new MutationObserver((mutations) => {
      const hasNewNodes = mutations.some(mutation => 
        mutation.type === 'childList' && mutation.addedNodes.length > 0
      );

      if (hasNewNodes) {
        this.setScrollPosition();
      }
    });

    this.observer.observe(this.messagesTarget, {
      childList: true,
      subtree: true
    });
  }

  disconnect() {
    if (this.observer) {
      this.observer.disconnect();
    }
  }

  setScrollPosition() {
    this.messagesTarget.scrollTop = this.messagesTarget.scrollHeight - this.messagesTarget.clientHeight 
  }

  submitForm(event) {
    if (event.key === "Enter" && !event.shiftKey) {
      event.preventDefault();
      const form = event.target.closest("form");
      form.submit();
    }
  }
}

Up to this point, yes. Don't worry it's coming though ;)

So glad to hear that! Folks like yourself are the exact people we made this course for so I'm very glad that you found it. You can definitely learn Rails and we are all here to help you to learn and support you along the way. Do not hesitate to reach out for additional help anytime! Welcome to Ruby, Rails, and GoRails!!

Yeah I should have mentioned that in the video so that was a detail oversight on my part. I was planning to update this video to mention it. Thank you for commenting about it though so others can be aware of it until I get an update out!

Funny you should say that because in the next video (spoiler alert!), where we add some more stimulus, I refactor our code to do this but still with the keydown event.

Joaquin Melogno - If you watch from timestamp 34:14 to 34:30 I do explain how that happens.

Thanks, Daniel!

I'm sure I'm guilty of it as well!!! Easy one to make especially as there is no mention of such behavior in the docs.

Thanks, Harsha! I'm glad to hear you enjoyed it!

Thanks, Dallas! Glad you enjoyed this one and hope it comes in handy for you!

That's really awesome to know about, thanks for sharing, Andrew!!!!

Hey Jared, thanks a bunch for the kind words!! I'm glad to hear that you are enjoying all of these courses that you have been going through lately. Thank you so much for taking the time to share your thoughts about it all with me/us!!! Don't hesitate to reach out if you need anything!

https://gorails.com/path - This would be a great place to get started.

Thank you so much, Gabriel!

Hey thanks Amit! Glad you are enjoying it.

Glad you found it so!

Simply calling Bunny.new.sync is going to raise that error as you are not instantiating a new instance of the Bunny class with any credentials. You are supposed to be using your credentials (library_id and access_key as shown in the screenshot below) in order to actually start making requests to Bunny.

Thanks! Glad you found it interesting. The follow-up episode for this, which comes out next week, where we explore how the code goes from bin/rails console to here should also prove to be interesting ;)

Today I learned that you can view the source code of a method that is available in the current context using the show_source command when in a call to binding.irb. To try it out put a binding.irb in an instance method for example. Create an object that responds to that message in your Rails console, call the method, and once you hit the binding.irb you can see what methods are available in the current context with the ls command. Find one that interests you and view the source by calling show_source foo (foo being the name of the method you want to view the source of) and you can quickly view the source code of that method.