-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Nv 2232 to in app notification center provider #3427
Nv 2232 to in app notification center provider #3427
Conversation
…ready-existing feat: add migration to create in app integration
NV-2232 🔔 to 📡 In-App Notification center provider on integration store
Why? (Context)Currently, the notification center configuration is scattered across multiple pages including the settings page. This creates for us multiple problems when it comes to understanding if a user has created a notification center integration and etc… What?
Definition of Done
SolutionLoom solution guide
|
…p-center-tab-in feat: remove hmac setting in settings
…-2333-update-api-to-use-new-hmac-flag-on
…ac-flag-on Nv 2333 update api to use new hmac flag on
…e-for-active-in feat: add check for active in app integration
feat: add framework select accordion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've found a few things, but I haven't checked the integration logic. I'll do the rest of the testing later.
apps/api/src/app/widgets/usecases/initialize-session/initialize-session.usecase.ts
Outdated
Show resolved
Hide resolved
All of these are now resolved. 3 was added to keep it aligned with the quickstart guide. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great work. Mostly light touch comments. 👏🏻
|
||
export async function createInAppIntegration() { | ||
// eslint-disable-next-line no-console | ||
console.log('start migration - in app integration'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's replace the console.logs for Logger from @nestjs/common
so we can also track the migrations with out telemetry tools. 🤔
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have not done it in migrations this far, but maybe it is a good idea
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We still need to change the file name and path, right? Still need help with that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes lets try to look at that tomorrow
No description provided.