Til Tracker

`FactoryBot::DuplicateDefinitionError` on dev server startup

Context: My development server (./bin/dev) failed to boot, reporting FactoryBot::DuplicateDefinitionError: Factory already registered: learning.
Cause: The factory_bot_rails gem was included in the group :development, :test do block in the Gemfile. This caused FactoryBot's Railtie to load factory definitions (spec/factories/*.rb) during development environment initialization (e.g., via Spring or initial boot), potentially conflicting with other initializers or running twice.
Resolution: I moved gem "factory_bot_rails" exclusively to the group :test do block in the Gemfile and ran rbenv exec bundle install.
Learning: I learned that gems intended solely for testing (like factory_bot_rails, shoulda-matchers, capybara) should typically only be included in the :test group in the Gemfile. Including them in :development can lead to unexpected behavior, errors during server startup, or unnecessary loading as their initializers might run inappropriately or cause conflicts.

Tags: testing dependencies factorybot gemfile environment-setup workflow

Learned on: April 15, 2024 Edit

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

Project cleanup: Removed unused Rails directories/files

What I Did: Performed project cleanup to align with the 37signals minimal approach.
Details: I identified and removed standard Rails directories/files not actively used: app/jobs/, app/mailers/, app/helpers/, app/controllers/concerns/, vendor/, script/, storage/, corresponding spec/helpers/ files. I removed configuration files for unused tools/services: .kamal/, .github/ (partially, CI kept), Dockerfile, .dockerignore, .rubocop.yml. I removed default Rails icons from public/.
Learning: I learned to regularly review the default Rails structure and remove components not essential to the application's core functionality to maintain simplicity and reduce clutter, checking project requirements.

Tags: workflow rails-core project-management

Learned on: April 13, 2024 Edit

Default checkboxes looked out of place in minimal UI

Context: The default browser checkboxes were not aligned with the clean, minimal aesthetic I desired for the application (37signals style).
Resolution: I created custom selection indicators using CSS (pseudo-elements ::before, ::after), with different styling for unselected, hover, and selected states. I used a circular indicator with a checkmark that appears when selected and hid the default checkbox (appearance: none or similar).
Learning: I learned that custom form controls can be built using the combination of visually hidden native inputs (for accessibility and functionality) paired with styled elements/pseudo-elements for visual presentation. This maintains native browser behaviors while allowing complete visual customization.

Tags: frontend project-management

Learned on: April 12, 2024 Edit

Learnings

`FactoryBot::DuplicateDefinitionError` on dev server startup

Request spec failure (`render_template` matcher missing)

Project cleanup: Removed unused Rails directories/files

Default checkboxes looked out of place in minimal UI