Add location field to Project model and schema and use that to find local competitors #43
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add a
locationfield to theProjectmodel and theProjectDetailsschema.This change allows capturing the geographical target audience of a project. This information is crucial for certain types of analysis, such as identifying relevant competitors.
The new field is included in the
ProjectDetailsPydantic schema used for agent interactions and is stored in the database. A migration was added to apply this schema change with a default value of 'Global'.The competitor analysis agent prompt was updated to potentially filter competitors based on the project's location if it's not 'Global', ensuring the identified competitors are relevant to the project's target market. The prompt also now requests a minimum of 20 competitors instead of 15.