e621 user page fix for faved posts
This commit is contained in:
@@ -1,13 +1,13 @@
|
||||
# How to use this codebase
|
||||
|
||||
- ALWAYS run `just tc` after making changes to ensure the codebase is typechecked.
|
||||
- ALWAYS run `srb tc` after making changes to Ruby files to ensure the codebase is typechecked.
|
||||
- ALWAYS run `bin/rspec <path_to_spec_file>` after a spec file is modified.
|
||||
- Run `tapioca dsl` if models or concerns are modified.
|
||||
- When modifying a specific file that has a corresponding spec file, run `bin/rspec <path_to_spec_file>` to run just that spec file.
|
||||
- After modifying a file that has a corresponding spec file, run `bin/rspec <path_to_spec_file>` to run just that spec file.
|
||||
- There are no view-specific tests, so if a view changes then run the controller tests instead.
|
||||
- For instance, if you modify `app/models/domain/post.rb`, run `bin/rspec spec/models/domain/post_spec.rb`. If you modify `app/views/domain/users/index.html.erb`, run `bin/rspec spec/controllers/domain/users_controller_spec.rb`.
|
||||
- At the end of a series of changes, ALWAYS run `just test` to run the entire test suite.
|
||||
- If specs are failing, then fix the failures, and rerun with `bin/rspec <path_to_spec_file>`.
|
||||
- ALWAYS construct ran commands ran with `run_terminal_cmd` to be compatible with fish shell.
|
||||
- ALWAYS suffix commands ran with `run_terminal_cmd` with `2>&1 | cat` to avoid terminal bugs.
|
||||
|
||||
# === BACKLOG.MD GUIDELINES START ===
|
||||
|
||||
|
||||
Reference in New Issue
Block a user