Skip to content

fix: persist aiTriageEnabled setting when creating page and product… - #18

Open
Adityakk9031 wants to merge 1 commit into
context-dot-dev:mainfrom
Adityakk9031:#16
Open

fix: persist aiTriageEnabled setting when creating page and product…#18
Adityakk9031 wants to merge 1 commit into
context-dot-dev:mainfrom
Adityakk9031:#16

Conversation

@Adityakk9031

Copy link
Copy Markdown

close #16

Description

This PR fixes a bug where the aiTriageEnabled setting was omitted from the SQL insert values when creating PAGE_CONTENT or PRODUCT_PRICE targets. This caused the option to always default to false in the database regardless of the user's input during monitor creation.

Changes

  • Updated the target creation route in src/app/api/websites/[id]/targets/route.ts to include aiTriageEnabled in the database insert query for page content and product price targets.

Verification

  • Tested locally by running the unit tests (npm run test) which all pass successfully.
  • Verified that target schemas correctly map the settings values upon insertion.

@Adityakk9031

Copy link
Copy Markdown
Author

@YahiaBakour have a look

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

aiTriageEnabled setting is not persisted when creating PAGE_CONTENT or PRODUCT_PRICE monitors

1 participant