compared to :none when paired
with :source-map.
By renouncing to :source-map option, the :whitespace
compilation/re-compilation time is very fast again.
The question for TDD practitioners is the following:
How fundamental is the availability of cljs's source-map in a TDD
again.
The question for TDD practitioners is the following:
How fundamental is the availability of cljs's source-map in a TDD workflow?
Could we renounce to it in favour of a quicker TDD loop? Do you see any
drawback in a TDD scenario for not having the source-map?
Honestly
to :none when paired
with :source-map.
By renouncing to :source-map option, the :whitespace
compilation/re-compilation time is very fast again.
The question for TDD practitioners is the following:
How fundamental is the availability of cljs's source-map in a TDD workflow
slow compared to :none when
paired with :source-map.
By renouncing to :source-map option, the :whitespace
compilation/re-compilation time is very fast again.
The question for TDD practitioners is the following:
How fundamental is the availability of cljs's source-map in a TDD
again.
The question for TDD practitioners is the following:
How fundamental is the availability of cljs's source-map in a TDD workflow?
Could we renounce to it in favour of a quicker TDD loop? Do you see any
drawback in a TDD scenario for not having the source-map?
Honestly, I use source-map
