-
Notifications
You must be signed in to change notification settings - Fork 432
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
feat: integrate formbricks in-app survey #1109
Conversation
formbricks.init({ | ||
environmentId: 'clnmmpeg01ci3o50fu5wy89zn', | ||
apiHost: 'https://app.formbricks.com', | ||
debug: false // remove when in production |
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.
Wouldn't debug be false for production?
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.
its false only? i dont understand what you mean?
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.
The comment says to remove in production
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.
Why would I remove debug: false
in production?
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.
The debug: false
is the same as removing! Its better to keep it as an option as its more verbose and can be enabled anytime if needed! And in my opinion, shouldn't be an issue at all
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.
Makes sense.
The comment just seemed confusing to me, as why would I be removing debug: false
in production. Since as you said it makes no difference.
Wouldn't it make more sense if debug was true with that comment or the comment was not there?
dashboard/pages/_app.tsx
Outdated
@@ -22,9 +25,25 @@ const printHiringMessage = () => { | |||
|
|||
if (typeof window !== 'undefined') { | |||
printHiringMessage(); | |||
formbricks.init({ | |||
environmentId: 'clnmmpeg01ci3o50fu5wy89zn', |
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.
should we import envId from some external var and not hardcode it
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.
yep, can we declare it here: https://github.com/tailwarden/komiser/blob/develop/dashboard/environments/environment.ts
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.
thats not an issue! it isn't sensitive. let me know if y'all still want me to shift it there
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, it is not sensitive, but it would be better to keep config variables outside in a centralized file so we can easily update them :)
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.
Done, please take a look now
Integrate Formbricks In-App Surveys