VSCode Task to create new packages

[martindsouza]

Create a new VSCode Task do to the following when run:

Paramater: package_name

Actions:

• Create two new files package_name.pks and package_name.pkb (note the file name extensions are now in scripts/project-config.sh
• Load each of the files from the associated templates in the templates folder
• Rename the package names to package_name

I find I'm doing this over and over again when creating a lot of new packages. It's a minor thing but could help people with new package development.

Notes:

• Slightly different than snippets in that this will create files
• Can be expanded for views (or other objects)

[rimblas]

Ohhh, yes please. I love this

[martindsouza]

@rimblas what do you think of just making one task that has two parameters:

• object_type (ex: view or package to start)
  • Note that package will create the spec and body files
• object_name

This way we wouldn't need a bunch of tasks. Concern is cluttering up drop down list when multiple projects are open.

[rimblas]

Yes,that sound reasonable. Although, I don't see view as a burden, meaning the task is not a big time saver.
I would default the type to package if possible.

[martindsouza]

@rimblas this is now in place. Can you please give it a try and provide your feedback?

[vitodcampanelli]

Files get created but I am getting the following error:
Edited: Replace image with shell output.

> Executing task: .vscode/scripts/gen_object.sh view test2 <

sed: invalid option -- 'a'
Usage: sed [OPTION]... {script-only-if-no-other-script} [input-file]...

  -n, --quiet, --silent
                 suppress automatic printing of pattern space
      --debug
                 annotate program execution
  -e script, --expression=script
                 add the script to the commands to be executed
  -f script-file, --file=script-file
                 add the contents of script-file to the commands to be executed
  --follow-symlinks
                 follow symlinks when processing in place
  -i[SUFFIX], --in-place[=SUFFIX]
                 edit files in place (makes backup if SUFFIX supplied)
  -l N, --line-length=N
                 specify the desired line-wrap length for the `l' command
  --posix
                 disable all GNU extensions.
  -E, -r, --regexp-extended
                 use extended regular expressions in the script
                 (for portability use POSIX -E).
  -s, --separate
                 consider files as separate rather than as a single,
                 continuous long stream.
      --sandbox
                 operate in sandbox mode (disable e/r/w commands).
  -u, --unbuffered
                 load minimal amounts of data from the input files and flush
                 the output buffers more often
  -z, --null-data
                 separate lines by NUL characters
      --help     display this help and exit
      --version  output version information and exit

If no -e, --expression, -f, or --file option is given, then the first
non-option argument is taken as the sed script to interpret.  All
remaining arguments are names of input files; if no input files are
specified, then the standard input is read.

GNU sed home page: <https://www.gnu.org/software/sed/>.
General help using GNU software: <https://www.gnu.org/gethelp/>.
rm: /Users/xyz/GitHub/starter-project-template-2/.vscode/tasks.json-bak: No such file or directory
sed: invalid option -- 'a'
Usage: sed [OPTION]... {script-only-if-no-other-script} [input-file]...

  -n, --quiet, --silent
                 suppress automatic printing of pattern space
      --debug
                 annotate program execution
  -e script, --expression=script
                 add the script to the commands to be executed
  -f script-file, --file=script-file
                 add the contents of script-file to the commands to be executed
  --follow-symlinks
                 follow symlinks when processing in place
  -i[SUFFIX], --in-place[=SUFFIX]
                 edit files in place (makes backup if SUFFIX supplied)
  -l N, --line-length=N
                 specify the desired line-wrap length for the `l' command
  --posix
                 disable all GNU extensions.
  -E, -r, --regexp-extended
                 use extended regular expressions in the script
                 (for portability use POSIX -E).
  -s, --separate
                 consider files as separate rather than as a single,
                 continuous long stream.
      --sandbox
                 operate in sandbox mode (disable e/r/w commands).
  -u, --unbuffered
                 load minimal amounts of data from the input files and flush
                 the output buffers more often
  -z, --null-data
                 separate lines by NUL characters
      --help     display this help and exit
      --version  output version information and exit

If no -e, --expression, -f, or --file option is given, then the first
non-option argument is taken as the sed script to interpret.  All
remaining arguments are names of input files; if no input files are
specified, then the standard input is read.

GNU sed home page: <https://www.gnu.org/software/sed/>.
General help using GNU software: <https://www.gnu.org/gethelp/>.
rm: /Users/xyz/GitHub/starter-project-template-2/views/test2.sql-bak: No such file or directory
Created: /Users/xyz/GitHub/starter-project-template-2/views/test2.sql

Terminal will be reused by tasks, press any key to close it.

[martindsouza]

@vitodcampanelli I think this could be a difference in our versions of sed. Can you please test what happens with this:

sed -i -bak "s/CHANGEME_TASKLABEL/$PROJECT_DIR_FOLDER_NAME/g" $VSCODE_TASK_FILE

[vitodcampanelli]

Edited: Replaced image with terminal output

sed: invalid option -- 'a'
Usage: sed [OPTION]... {script-only-if-no-other-script} [input-file]...

  -n, --quiet, --silent
                 suppress automatic printing of pattern space
      --debug
                 annotate program execution
  -e script, --expression=script
                 add the script to the commands to be executed
  -f script-file, --file=script-file
                 add the contents of script-file to the commands to be executed
  --follow-symlinks
                 follow symlinks when processing in place
  -i[SUFFIX], --in-place[=SUFFIX]
                 edit files in place (makes backup if SUFFIX supplied)
  -l N, --line-length=N
                 specify the desired line-wrap length for the `l' command
  --posix
                 disable all GNU extensions.
  -E, -r, --regexp-extended
                 use extended regular expressions in the script
                 (for portability use POSIX -E).
  -s, --separate
                 consider files as separate rather than as a single,
                 continuous long stream.
      --sandbox
                 operate in sandbox mode (disable e/r/w commands).
  -u, --unbuffered
                 load minimal amounts of data from the input files and flush
                 the output buffers more often
  -z, --null-data
                 separate lines by NUL characters
      --help     display this help and exit
      --version  output version information and exit

If no -e, --expression, -f, or --file option is given, then the first
non-option argument is taken as the sed script to interpret.  All
remaining arguments are names of input files; if no input files are
specified, then the standard input is read.

GNU sed home page: <https://www.gnu.org/software/sed/>.
General help using GNU software: <https://www.gnu.org/gethelp/>.

[martindsouza]

@vitodcampanelli can you also include the exact command that you ran? Find it odd it's complaining about -a when we don't use that.

[vitodcampanelli]

@martindsouza Here is the command

sed -i -bak "s/CHANGEME_TASKLABEL/$PROJECT_DIR_FOLDER_NAME/g" $VSCODE_TASK_FILE

[martindsouza]

@vitodcampanelli what are the values for $PROJECT_DIR_FOLDER_NAME and $VSCODE_TASK_FILE (want to make sure no special characters in path or spaces