-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hw(notifications): In-app notifications #76499
Conversation
This reverts commit 7853543.
🚨 Warning: This pull request contains Frontend and Backend changes! It's discouraged to make changes to Sentry's Frontend and Backend in a single pull request. The Frontend and Backend are not atomically deployed. If the changes are interdependent of each other, they must be separated into two pull requests and be made forward or backwards compatible, such that the Backend or Frontend can be safely deployed independently. Have questions? Please ask in the |
This PR has a migration; here is the generated SQL for --
-- Create model NotificationHistory
--
CREATE TABLE "sentry_notificationhistory" ("id" bigint NOT NULL PRIMARY KEY GENERATED BY DEFAULT AS IDENTITY, "date_updated" timestamp with time zone NOT NULL, "date_added" timestamp with time zone NULL, "user_id" bigint NULL, "title" varchar NOT NULL, "description" varchar NOT NULL, "status" varchar NOT NULL, "source" varchar NOT NULL, "content" text NOT NULL, "team_id" bigint NULL);
ALTER TABLE "sentry_notificationhistory" ADD CONSTRAINT "sentry_notificationhistory_team_id_7d5d21c6_fk_sentry_team_id" FOREIGN KEY ("team_id") REFERENCES "sentry_team" ("id") DEFERRABLE INITIALLY DEFERRED NOT VALID;
ALTER TABLE "sentry_notificationhistory" VALIDATE CONSTRAINT "sentry_notificationhistory_team_id_7d5d21c6_fk_sentry_team_id";
CREATE INDEX CONCURRENTLY "sentry_notificationhistory_user_id_299fa975" ON "sentry_notificationhistory" ("user_id");
CREATE INDEX CONCURRENTLY "sentry_notificationhistory_team_id_7d5d21c6" ON "sentry_notificationhistory" ("team_id");
--
-- Create constraint user_xor_team_required on model notificationhistory
--
ALTER TABLE "sentry_notificationhistory" ADD CONSTRAINT "user_xor_team_required" CHECK ((("user_id" IS NULL AND "team_id" IS NOT NULL) OR ("user_id" IS NOT NULL AND "team_id" IS NULL))) NOT VALID;
ALTER TABLE "sentry_notificationhistory" VALIDATE CONSTRAINT "user_xor_team_required"; |
❌ 67 Tests Failed:
View the top 3 failed tests by shortest run time
To view individual test run time comparison to the main branch, go to the Test Analytics Dashboard |
This pull request has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you add the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you remove the label "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
todo