You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have no internet connection, our app should still work correctly when running locally. Unfortunately the app fails under these circumstances in at least a couple ways:
The test suite fails in tests that render the base template due to <link>/<script> tags with external urls (e.g.: <link href="https://maxcdn.bootstrapcdn.com/font-awesome/4.6.1/css/font-awesome.min.css" rel="stylesheet"/>). It's not clear why these tests are actually making the requests to those URLs instead of just rendering the page body as a string.
When making changes to an application that advance the state (uploading a resume, adding a video interview, completing a payment), Hubspot requests are sent in tasks. Those requests fail, and the exceptions stop execution entirely
Acceptance criteria
Test suite runs successfully while the host machine is offline
While offline, changes can be made to an application without breaking due to failed Hubspot requests (errors are logged, but the changes are still made)
Nice to have
Fail the test suite if any external requests are detected. There might be a library/plugin for this?
The text was updated successfully, but these errors were encountered:
Hubspot tasks will not run if MITOL_HUBSPOT_API_PRIVATE_TOKEN is not set. If offline, just unset this variable. Application state still seems to advance if offline.
Commenting out HUBSPOT_API_KEY allows me to run bootcamps-ecommerce locally without an internet connection. @mbertrand, do you think we can close this?
If you have no internet connection, our app should still work correctly when running locally. Unfortunately the app fails under these circumstances in at least a couple ways:
<link>
/<script>
tags with external urls (e.g.:<link href="https://maxcdn.bootstrapcdn.com/font-awesome/4.6.1/css/font-awesome.min.css" rel="stylesheet"/>
). It's not clear why these tests are actually making the requests to those URLs instead of just rendering the page body as a string.Acceptance criteria
Nice to have
The text was updated successfully, but these errors were encountered: