Til Tracker

Request spec failure (`render_template` matcher missing)

Context: My request spec failed: Failure/Error: expect(response).to render_template(:new) ... assert_template has been extracted to a gem. To continue using it, add gem 'rails-controller-testing' to your Gemfile. The render_template matcher in RSpec request specs relies on functionality (assert_template) that is no longer part of Rails core.
Resolution: I added gem 'rails-controller-testing' to the :test group in the Gemfile and ran bundle install.
Learning: I learned to be aware that testing helpers previously included in Rails core might be extracted into separate gems in newer versions. Error messages usually indicate the required gem (rails-controller-testing for render_template, assigns, assert_template).

Tags: testing rails-core rspec request-spec dependencies gem controller-testing gemfile

Learned on: April 14, 2024 Edit

Feature: Implemented tag filtering

Action: I implemented the tag filtering feature.
Details: I added a tag_list helper to the Learning model (simple tags.split(',').map(&:strip)). I updated LearningsController#index to filter by params[:tag] (where("tags LIKE ?", "%#{params[:tag]}%")) and collect unique tags for the view (Learning.pluck(:tags).flat_map { |t| t.split(',') }.uniq). I updated index.html.erb with a turbo_frame_tag around the list, clickable tag links (link_to tag, learnings_path(tag: tag)), and filter controls. I added basic CSS styling for tags.
Learning: I learned that simple string-based tags (comma-separated) can be made functional for filtering using basic Rails querying (LIKE or string_to_array in PG) and Turbo Frames for efficient UI updates without full page reloads, adhering to the 37signals principle of starting simple.

Tags: feature rails-core model controller view tags filtering turbo hotwire sql like css ui 37signals

Learned on: April 14, 2024 Edit

NoMethodError: undefined method `learned_on` on `new` learning page

Context: The new.html.erb view tried to access @learning.learned_on to set the default value for the date field (value: @learning.learned_on || Date.today), causing NoMethodError.
Resolution: I changed the date_field value in the view to just value: Date.today. The @learning instance created by LearningsController#new (Learning.new) is unsaved and doesn't have attributes populated from database defaults until saved.
Learning: I learned to be mindful of when database defaults are applied (on save) versus needing to set defaults explicitly in the controller (Model.new(attr: default)) or view (value: default) for new object instances presented in forms.

Tags: rails-core controller view form model date nomethoderror database default

Learned on: April 13, 2024 Edit

Feature: Implemented retroactive learning logging

Feature: I implemented retroactive learning logging.
Details: I added learned_on date field (type: :date, null: false, default: 'CURRENT_DATE') to the Learning model/migration. I updated the controller learning_params to permit :learned_on. I updated index sorting to use ORDER BY learned_on DESC, created_at DESC. I added a date_field to _form.html.erb. I updated index view display.
Learning: I learned that using SQL default CURRENT_DATE is effective for database-level defaults upon record creation. However, for new, unsaved records in a form, a default needs to be set in the view (e.g., <%= form.date_field :learned_on, value: Date.today %>) or controller (@learning = Learning.new(learned_on: Date.today)).

Tags: feature rails-core model migration controller view form database sql date

Learned on: April 13, 2024 Edit