Thanks very much @rockymeza this worked for me.
I followed your instructions (using SENTRY_DSN everywhere & adding it to my redwood.toml) and setting SENTRY_DSN instead of SENTRY_AUTH_TOKEN in the .env.
given that it’s React, I safetied the /web init, as you did in the /api usage
const [sentryInitialized, setSentryInitialized] = React.useState(false)
if (process.env.SENTRY_DSN && !sentryInitialized) {
setSentryInitialized(true)
Sentry.init({
dsn: process.env.SENTRY_DSN,
})
}
However, when I wrap my graphql as suggested all of my relations stop auto including
Very odd…
This code worked before loading a whole pile of relations automatically
const attendee = await db.attendee.findUnique({
where: { id },
})
.then(thenDebug(`[${__file}] attendee ~ db.attendee.findUnique`))
.catch(logger.error)
I wonder if it has something to do with the redwood object for the table
export const Attendee = {
event: (_obj, { root }: ResolverArgs<ReturnType<typeof Attendee>>) =>
db.attendee.findUnique({ where: { id: root.id } }).event(),
user: (_obj, { root }: ResolverArgs<ReturnType<typeof Attendee>>) =>
db.attendee.findUnique({ where: { id: root.id } }).user(),
answers: (_obj, { root }: ResolverArgs<ReturnType<typeof Attendee>>) =>
db.attendee.findUnique({ where: { id: root.id } }).answers(),
agreement: (_obj, { root }: ResolverArgs<ReturnType<typeof Attendee>>) =>
db.attendee.findUnique({ where: { id: root.id } }).agreement(),
guests: (_obj, { root }: ResolverArgs<ReturnType<typeof Attendee>>) =>
db.attendee.findUnique({ where: { id: root.id } }).guests(),
forwards: (_obj, { root }: ResolverArgs<ReturnType<typeof Attendee>>) =>
db.attendee.findUnique({ where: { id: root.id } }).forwards(),
};
It’s as if this is no longer used…