-
Notifications
You must be signed in to change notification settings - Fork 59
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: explicitly define content type #235
Conversation
Signed-off-by: Pianist038801 <[email protected]>
83cd231
to
c3917f0
Compare
Codecov Report
@@ Coverage Diff @@
## master #235 +/- ##
=========================================
Coverage ? 63.45%
=========================================
Files ? 365
Lines ? 7913
Branches ? 1388
=========================================
Hits ? 5021
Misses ? 2892
Partials ? 0 Continue to review full report at Codecov.
|
@jsonporter just checking-in here to see if we can get this PR reviewed and merged :). It seems like this is tagged to go out in the 0.18.1 release — any idea when that would be? |
Signed-off-by: Jason Porter <[email protected]>
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.
Had to fix: added port 7777 because 5555 (default for webpack-plugin-serve
) is now used by OSX Big Sur. Otherwise its good to go.
# [0.31.0](http://github.com/lyft/flyteconsole/compare/v0.30.0...v0.31.0) (2021-11-16) ### Features * explicitly define content type ([#235](http://github.com/lyft/flyteconsole/issues/235)) ([0cbcd13](http://github.com/lyft/flyteconsole/commit/0cbcd134eda192424d59a19bc0f57256e314181d))
🎉 This PR is included in version 0.31.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This PR makes MIME type for requests to /assets/main.js served as application/javascript
Type
Are all requirements met?
Tracking Issue
fixes flyteorg/flyte#1735
Follow-up issue
NA