We can now see exactly what's wrong with our code in Sentry. So let's do the obvious next step. That is, fix it. I'll update the checkout function to alert, checking out items.
Of course, in a real application, this would be a more functional fix, but you get the idea. json file, I'll update the version of the project. Finally, back in the Sentry dashboard, where I've still got the issue open. I'll click the arrow next to the Resolve button and select that this is resolved in the next release.
Sweet! Look at us knocking out issues! Just to note, this could also be done in a future release or even automatically via a commit if GitHub is set up with Sentry. But this method works great too.
Alright, now I'll do the same for the issue logged without the source maps by visiting the Issues page. selecting the issue, and once again using the resolve button at the top of the issues table. When I refresh the page, the issue now disappears, and these wonderful little robots are letting us know that our code is good to go. Should our issue ever be triggered again for some reason, it will appear here again, but Sentry will mark it as a regression.
Finally, if this were a real project with a production environment, I'd also now deploy my application. We can now see exactly what's wrong with our code in Sentry. So let's do the obvious next step. That is, fix it.
I'll update the checkout function to alert, checking out items. Of course, in a real application, this would be a more functional fix, but you get the idea. json file, I'll update the version of the project. Finally, back in the Sentry dashboard, where I've still got the issue open.
I'll click the arrow next to the Resolve button and select that this is resolved in the next release. Sweet! Look at us knocking out issues! Just to note, this could also be done in a future release or even automatically via a commit if GitHub is set up with Sentry.
But this method works great too. Alright, now I'll do the same for the issue logged without the source maps by visiting the Issues page. selecting the issue, and once again using the resolve button at the top of the issues table. When I refresh the page, the issue now disappears, and these wonderful little robots are letting us know that our code is good to go.
Should our issue ever be triggered again for some reason, it will appear here again, but Sentry will mark it as a regression. Finally, if this were a real project with a production environment, I'd also now deploy my application.