songtianlun
23992ec4b2
- Implement before_action to ensure users are logged in - Add logged_in_user method to handle redirection - Update user fixture to include new user - Enhance integration tests to check for login requirement This commit introduces user authentication checks for the edit and update actions in the UsersController. It ensures that only logged-in users can access these actions, improving the security of the application. Additionally, integration tests have been updated to verify that users are redirected to the login page if they attempt to edit or update their information without being logged in. |
||
|---|---|---|
| .github | ||
| .kamal | ||
| app | ||
| bin | ||
| config | ||
| db | ||
| lib/tasks | ||
| log | ||
| public | ||
| script | ||
| storage | ||
| test | ||
| tmp | ||
| vendor | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .rubocop.yml | ||
| .ruby-version | ||
| config.ru | ||
| Dockerfile | ||
| Gemfile | ||
| Gemfile.lock | ||
| Guardfile | ||
| package-lock.json | ||
| package.json | ||
| Procfile.dev | ||
| Rakefile | ||
| README.md | ||
| yarn.lock | ||
README
This README would normally document whatever steps are necessary to get the application up and running.
Things you may want to cover:
-
Ruby version
-
System dependencies
-
Configuration
-
Database creation
-
Database initialization
-
How to run the test suite
-
Services (job queues, cache servers, search engines, etc.)
-
Deployment instructions
-
...