Skip to content

Conversation

@jeffmaki
Copy link
Contributor

@jeffmaki jeffmaki commented Dec 16, 2025

Integration of the Sentry SDK for workspaces JS errors

@jeffmaki jeffmaki requested a review from cyrossignol December 16, 2025 20:26
Copy link
Collaborator

@cyrossignol cyrossignol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks cool. Unfortunately, I don't think this is plug-and-play with our current setup. Did you get it to work locally?

Dockerfile Outdated
ENV VITE_IMAGERY_SCHEMA=https://raw.githubusercontent.com/TaskarCenterAtUW/tdei-tools/main/docs/imagery-layer/schema.json
ENV VITE_IMAGERY_EXAMPLE_URL=https://raw.githubusercontent.com/TaskarCenterAtUW/tdei-tools/main/docs/imagery-layer/example.json
ENV VITE_LONG_FORM_QUEST_SCHEMA=https://raw.githubusercontent.com/TaskarCenterAtUW/tdei-tools/refs/heads/main/docs/quest-definition/schema.json
ENV VITE_LONG_FORM_QUEST_EXAMPLE_URL=https://raw.githubusercontent.com/TaskarCenterAtUW/tdei-tools/refs/heads/main/docs/quest-definition/example.json
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we please drop the defaults so there's only one place to maintain these? I'd prefer to update workspaces-stack/example.env. We also want the build to fail when any of these are missing, and Docker will bail when there are no defaults set.

Copy link
Contributor Author

@jeffmaki jeffmaki Dec 16, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure thing--these were the values in the readme though, so allowed one to more easily setup a dev instance. I removed.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! These need to be ARGs, though (with no default empty string). ENVs don't work at build time.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it. Added a comment since that's not intuitive.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good call, thanks. Sorry, can you please remove the empty string defaults? Those will short-circuit Docker's missing arg checks.

@jeffmaki
Copy link
Contributor Author

Looks cool. Unfortunately, I don't think this is plug-and-play with our current setup. Did you get it to work locally?

It did work locally yes.

@cyrossignol
Copy link
Collaborator

One more thing, this isn't a full npm package upgrade, right? I see a lot of changes in the lock file. IIRC, there's some dependency in there that broke something, and I didn't have time before the demo to figure it out.

@jeffmaki
Copy link
Contributor Author

One more thing, this isn't a full npm package upgrade, right? I see a lot of changes in the lock file. IIRC, there's some dependency in there that broke something, and I didn't have time before the demo to figure it out.

I did run npm audit yes. What was broken?

@jeffmaki
Copy link
Contributor Author

@cyrossignol Can you approve this if you're okay with these changes now please?

@cyrossignol
Copy link
Collaborator

Please don't merge that review-queue branch along with this PR! For testing, we can create a separate branch with everything merged together.

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.

3 participants