Closed earthbound19 closed 6 years ago
Fair point, however that would be a breaking change so I'm going to give it some more thought.
My current main reasons not to do this are:
Reasons to do change this behaviour:
Now that I am thinking of it, I was already thinking about adding some more production output (CONTINUED for instance) which is currently missing in Wrap, so having a --production
flag might be better suited for this.
As you might see, I went for a --production
flag (alternatively you can use -p
). :slightly_smiling_face:
I would guess that people would want a dozen little switches to turn a dozen little features on or off. I would anyway (so, a --scene-numbers
switch and a --continueds
switch, etc.). Maybe --production
could switch a bunch of things on (whatever other production features you're planning to add), with contradicting switches overriding it.
That's a long-term goal, currently there are only scene-numbers and I wanted to keep the amount of toggles low for now (to prevent ending up removing a bunch of toggles because some default changed) :slightly_smiling_face: Also Continueds aren't used as much anymore so I'm not entirely sure I'll end up adding them (the rules are surprisingly complex to implement) unless there is a demand for it, of course :)
The majority of uses for screenplays (in that most of them are spec and not in production) is to not use scene numbers. I suggest that instead of a
--no-scene-numbers
flag to disable this feature, there be a--scene-numbers
flag to enable it. Or have a--scene-numbers
flag which expects aTrue
orFalse
or1
or0
value, with the default0
if the flag is omitted (I don't know whether Go and/or CLI conventions, uh, go for that kind of thing).