dalehenrich/superDoit

Issues

• need to be able to conditionally use 3.7.0 or 3.7.1 with install.sh

  #74 opened 8 months ago by dalehenrich
  0

• in 3.7.0 the path to the superDoit project embedded in productTree was changed ... the productTree scripts need to reflect this change

  #73 opened 9 months ago by dalehenrich
  0

• SUPERDOIT_DIR is too sticky ...

  #68 opened 9 months ago by dalehenrich
  1

• add Rowan 3 tests to github CI when 3.7.1 ships

  #71 opened a year ago by dalehenrich
  0

• need to support Rowan 3 .solo scripts: add superdoit_rowan3_solo

  #70 opened a year ago by dalehenrich
  1

• v4.2, needs to use setup-superDoit@v3 (I think) as part of ci.yml

  #69 opened a year ago by dalehenrich
  1

• Referencing classes from incoming projects

  #67 opened a year ago by dalehenrich
  0

• Better .stone/.topaz support for GsDevKit_stones

  #66 opened a year ago by dalehenrich
  0

• compile doit section when showing help ... as shortcut to get live compile errors in all methods

  #65 opened 2 years ago by dalehenrich
  0

• port smalltalkCI to superDoit and GsDevKit_stones

  #63 opened 2 years ago by dalehenrich
  0

• ChildError should not trigger DEBUGGEM

  #64 opened 2 years ago by dalehenrich
  0

• versionReport.xxxx should include Rowan version/present plus superDoit version

  #62 opened 2 years ago by dalehenrich
  0

• starting with 3.7.0, use `System waitForDebug` when waiting for --debugGem attach

  #61 opened 2 years ago by dalehenrich
  1

• when strings are returned from a superDoit script we should avoid STONifying

  #60 opened 2 years ago by dalehenrich
  0

• Using superdoit without setting environment

  #55 opened 2 years ago by LisaAlmarode
  6

• (v3) if superDoit is already loaded, use the loaded variant of the project when running scripts ...

  #59 opened 2 years ago by dalehenrich
  0

• add default --debugGem option

  #58 opened 2 years ago by dalehenrich
  0

• convert to use 3.6.5 with an extent0.rowan.dbf included in product tree

  #57 opened 2 years ago by dalehenrich
  0

• command line with positional args containing white space not handled correctly

  #56 opened 2 years ago by dalehenrich
  0

• version.txt is required in order to use .stone superdoit scripts

  #54 opened 3 years ago by LisaAlmarode
  0

• typo in gemstone/productTree/superdoit_solo

  #53 opened 3 years ago by dalehenrich
  0

• wait until preSpecDoit is called to expand specurls ...

  #52 opened 3 years ago by dalehenrich
  0

• Execution always uses -L; can't ever get -r to work

  #49 opened 3 years ago by LisaAlmarode
  4

• currently superDoit defaults to printString if STON not installed ... should use JSON instead

  #51 opened 3 years ago by dalehenrich
  1

• if extent not read-only, get instrusive warning

  #48 opened 3 years ago by LisaAlmarode
  1

• Need --waitForDebugGem option

  #47 opened 3 years ago by dalehenrich
  0

• better debuggem support ....

  #37 opened 3 years ago by dalehenrich
  2

• consider allowing user to specify the extent to use for a superdoit_solo

  #39 opened 3 years ago by LisaAlmarode
  10

• examples/gemstone scripts need work

  #46 opened 3 years ago by LisaAlmarode
  0

• Specifications for positional arguments

  #45 opened 3 years ago by LisaAlmarode
  0

• default help output needs some work

  #44 opened 3 years ago by LisaAlmarode
  0

• Handling of sections that appear more than once in a script

  #43 opened 3 years ago by LisaAlmarode
  0

• superdoit_* ... -h and usage message if invoked without script arg

  #42 opened 3 years ago by dalehenrich
  0

• Request to be able to add to gem arguments from within superdoit script

  #41 opened 3 years ago by LisaAlmarode
  2

• various nits on versionReport examples

  #40 opened 3 years ago by LisaAlmarode
  1

• superdoit_solo and friends handle -h

  #38 opened 3 years ago by LisaAlmarode
  0

• `-1` is problematic as script argument ...

  #35 opened 3 years ago by dalehenrich
  1

• get rid of the `ExitClientError: explicit process exit` message ... exit status is enough ...

  #36 opened 3 years ago by dalehenrich
  1

• if -C topaz option passed in from .solo/.stone script it ends up masking the -C option used to define the solo extent

  #34 opened 3 years ago by dalehenrich
  0

• need to trim blanks on filenames in input section

  #33 opened 3 years ago by dalehenrich
  0

• .solo script does not accept topaz arguments...

  #31 opened 3 years ago by dalehenrich
  0

• long option names need to be valid selectors ...

  #32 opened 3 years ago by dalehenrich
  0

• v3 ... revamp handling of input, spec*, and extension method commands

  #30 opened 3 years ago by dalehenrich
  1

• classmethod section makes sense ...

  #29 opened 3 years ago by dalehenrich
  0

• a Rowan extent should not be required as a solo extent ... the Rowan sections would be ignored if present

  #28 opened 3 years ago by dalehenrich
  0

• use setup-superDoit to install superDoit for use in github actions ...

  #24 opened 3 years ago by dalehenrich
  0

• instead of 4 separate workflows, one workflow that runs all 4 tests

  #26 opened 3 years ago by dalehenrich
  1

• Move the `setup stones for tests` logic to a dev shell script ... perhaps even to setup-superDoit?

  #25 opened 3 years ago by dalehenrich
  1

• looks like we're not doing CI testing for 3.4.0 .stone ...

  #23 opened 3 years ago by dalehenrich
  1

• superdoit .stone scripts should not depend upon FileStream class ...

  #22 opened 3 years ago by dalehenrich
  1