29 lines
1.6 KiB
Markdown
Executable File
29 lines
1.6 KiB
Markdown
Executable File
# Qwen Code Customization
|
|
|
|
## Project Context
|
|
- Working on a Ruby on Rails project named "aperonight"
|
|
- Using Docker for containerization
|
|
- Following Ruby version 3.1.0 (as indicated by .ruby-version)
|
|
- Using Bundler for gem management (Gemfile)
|
|
- Using Node.js for frontend assets (package.json likely present)
|
|
|
|
## Preferences
|
|
- Prefer to use Ruby and Rails conventions
|
|
- Follow Docker best practices for development environments
|
|
- Use standard Ruby/Rails project structure
|
|
- When creating new files, follow Rails conventions
|
|
- When modifying existing files, maintain consistency with current code style
|
|
- Use git for version control (as seen in .gitignore)
|
|
- Prefer to work with the project's existing toolchain (Bundler, etc.)
|
|
|
|
## Behavior
|
|
- When asked to make changes, first understand the context by examining relevant files
|
|
- When creating new files, ensure they follow project conventions
|
|
- When modifying files, preserve existing code style and patterns
|
|
- When implementing new features, suggest appropriate file locations and naming conventions
|
|
- When debugging, suggest using the project's existing test suite and development tools
|
|
- When suggesting changes, provide clear explanations of why the change is beneficial
|
|
|
|
## Qwen Added Memories
|
|
- We've implemented the checkout process with name collection for tickets that require identification. We've added first_name and last_name fields to the tickets table, updated the Ticket model with validations, added new routes and controller actions, created a view for collecting names, and updated the JavaScript controller. The database migration needs to be run in the Docker environment when the gem issues are resolved.
|