Skip to content
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

Merged
merged 2 commits into from
Nov 16, 2021

Conversation

Pianist038801
Copy link
Contributor

This PR makes MIME type for requests to /assets/main.js served as application/javascript

Type

  • Bug Fix
  • Feature
  • Plugin

Are all requirements met?

  • Code completed
  • Smoke tested
  • Unit tests added
  • Code documentation added
  • Any pending items have an associated Issue

Tracking Issue

fixes flyteorg/flyte#1735

Follow-up issue

NA

@Pianist038801 Pianist038801 force-pushed the feat/explicitly-define-content-type branch from 83cd231 to c3917f0 Compare November 9, 2021 17:17
@codecov
Copy link

codecov bot commented Nov 9, 2021

Codecov Report

❗ No coverage uploaded for pull request base (master@a64e138). Click here to learn what that means.
The diff coverage is n/a.

Impacted file tree graph

@@            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.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a64e138...fac65e1. Read the comment docs.

@btang-stripe
Copy link

@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?

Copy link
Contributor

@jsonporter jsonporter left a 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.

@flyte-bot
Copy link
Collaborator

🎉 This PR is included in version 0.31.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@anrusina anrusina deleted the feat/explicitly-define-content-type branch January 14, 2022 20:47
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.

[UI Feature] Explicitly define content-type as 'application/javascript' for requests to assets/main.js
4 participants