-
Notifications
You must be signed in to change notification settings - Fork 15
[TASK] enable generation of sourcemaps #20
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
Open
pniederlag
wants to merge
1
commit into
kaystrobach:master
Choose a base branch
from
pniederlag:feature/sourcemap
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
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
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
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.
from my POV i would rather say, dev context AND enableDebugMode, would also change the less parser accordingly - respecting the context feels more natural here.
https://github.com/kaystrobach/TYPO3.dyncss_less/blob/master/Classes/Parser/LessParser.php#L104
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.
whats your opinion?
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.
nope, please not. ;)
There are times when you need to debug "ad hoc", and I hate it when I have to login to the BE in order to adapt a setting. As EM config is serialized array it's really tough to change from CLI (Not sure wether typo3_console supports it?).
Also it is really tough to keep ext_conf_template.txt settings different per environment, when you have everything in SCM and have deployments with adapted settings (.env, HostConfiguration) per site/installation.
So I am in big favor of having a simple mechanism to toggle this feature, without EM settings ;)
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.
ok, then i would opt for deprecating the debugMode and simply switch to contexts ...
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.
What's wrong with having two different options?
In general TYPO3 Context will take care of properly enabling/disabling the feature
If you want to use sourcemaps, but for some reason(production?) don't want to set development context, well then enableDebugMode.
I don't see the cost involved of keeping enableDebugMode while prefering Context.