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
This combination of tools could be built into our process to expedite resolving style issues.
Does the code reformatting require review for correctness of style, or even error-free functionality?
Do we want it to run as part of currently read-only operations like grunt validate?
Should we bundle it with other code formatting and cleanup tools, for a top level grunt optimize task? This seems to imply we don't group it with validate or the main build process, and instead provide it to developers to use reactively.
Can we streamline how IDEs might apply formatting correction automatically?
This issue needs someone to set up the tools, run edge case experiments, see what IDE integration with phpstorm, sublime, or atom might look like, and come back with findings so we can make decisions on next steps.
The text was updated successfully, but these errors were encountered:
This combination of tools could be built into our process to expedite resolving style issues.
grunt optimize
task? This seems to imply we don't group it with validate or the main build process, and instead provide it to developers to use reactively.This issue needs someone to set up the tools, run edge case experiments, see what IDE integration with phpstorm, sublime, or atom might look like, and come back with findings so we can make decisions on next steps.
The text was updated successfully, but these errors were encountered: