chore: grouped prompt-enhancer-percentage and criteria check under ai…#880
chore: grouped prompt-enhancer-percentage and criteria check under ai…#880Anushtha-Rathore wants to merge 1 commit intoWalkover-Web-Solution:testingfrom
Conversation
![windsurf-bot[bot]](https://avatars.githubusercontent.com/in/1066231?s=60&v=4){kind=small}
| { | ||
| $set: { | ||
| "ai_updates.prompt_enhancer_percentage": prompt_enhancer_percentage, | ||
| "ai_updates.criteria_check": criteria_check | ||
| } | ||
| } |
There was a problem hiding this comment.
This change modifies where prompt_enhancer_percentage and criteria_check are stored in the document structure. Consider adding a migration script to move existing data from the root level to the new ai_updates object structure to maintain consistency across all documents.
| "ai_updates.prompt_enhancer_percentage": 1, | ||
| "ai_updates.criteria_check": 1 |
There was a problem hiding this comment.
This change moves prompt_enhancer_percentage and criteria_check under an ai_updates object, which is good for organization. However, I don't see any migration strategy mentioned to handle existing data that might have these fields at the root level. Without a migration, this could cause data access issues for existing records. Consider adding a migration or ensuring backward compatibility during the transition period.
| "ai_updates.prompt_enhancer_percentage": prompt_enhancer_percentage, | ||
| "ai_updates.criteria_check": criteria_check |
There was a problem hiding this comment.
Make sure to update any code that reads prompt_enhancer_percentage and criteria_check directly from the document root to now access them via the ai_updates object. This includes any frontend code or other services that might be querying these fields.
1 participant
chore: grouped prompt-enhancer-percentage and criteria check under ai-updates