-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
feat(nuxt): Base decision on source maps upload only on Nuxt source map settings #15859
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
Merged
Merged
Changes from 8 commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
015bcc1
wip: revamped source maps for nuxt
s1gr1d 6748475
clean up code 1
s1gr1d 0d34bb9
add tests 1
s1gr1d f56e7d8
add tests 2
s1gr1d 3aafc13
add test for deleteFilesAfterUpload
s1gr1d 878b13d
remove white spaces
s1gr1d a9165dc
add debug log to add rollup plugin
s1gr1d 0909745
Merge branch 'develop' into sig/source-maps-nuxt
s1gr1d 479aa8f
update "enabled" log
s1gr1d File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
l: should we keep the "be aware" sentence here? as far as I understand, we'd emit an explicit warning anyway via
validateDifferentSourceMapSettings
, right?The reason why I'm thinking about this is that this should be a "success message", right? I just want to convey this and not risk users thinking they did something wrong or mistake the message with a warning. Especially with "hidden" I could see users being confused.
What about something like this?
Which brings me to an alternative question/idea: Do we even need this message at all? In case of users already having source maps enabled, there's nothing for us to do anyway, right? Not saying it has to go, just food for thought :)
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.
I'll change this to your suggestion but will keep it to show it when
debug
is enabled :)