scripts: Add script for changing all abs paths

[johannes-wolf]

This allows installing cetz with all paths in all *.typ files changed to relative ones.
@Andrew15-5: Please test this via just package <your-directory> --relative-paths.

As soon as Typst supports changing the package path, this cursed script must get removed.

[Andrew15-5]

BTW, it's not great when you import the same published package multiple times. I had an issue (with cetz) where I thought I've changed the version, but actually I imported the same old version in different files. So I advise you to import external libraries somewhere once and then import that local file everywhere where you need external library API.

You can very easily forget to update all files that import the same package.

src/anchor.typ
1:#import "@preview/oxifmt:0.2.0": strfmt

src/draw/grouping.typ
1:#import "@preview/oxifmt:0.2.0": strfmt

src/coordinate.typ
3:#import "@preview/oxifmt:0.2.0": strfmt

src/util.typ
1:#import "@preview/oxifmt:0.2.0": strfmt

[Andrew15-5]

I test some basic stuff, and it works:

#import "./cetz/0.2.0/src/lib.typ" as cetz

#cetz.canvas({
  import cetz.draw: *
  circle(())
})

#cetz.canvas({
  import cetz.draw: *
  import cetz.plot
  plot.plot(size: (5, 5), {
    plot.add(domain: (-10, 10), x => x * x)
  })
})

#367 (comment):

I think Typst checks/imports everything first, before compiling, so the test is just "does it compile a document?" Although I'm not sure.

Indeed, it checks for everything, therefore if there is an invalid import, then the error must show up. So any "import cetz and compile" test should prevent any relative path bugs.

[Andrew15-5]

Note this:

So the only thing that won't be noticed right away [by the compiler] is if if statement block isn't run or loop isn't run or a function isn't called, but all root imports/includes will 100% be checked.

[johannes-wolf]

Note this:

So the only thing that won't be noticed right away [by the compiler] is if if statement block isn't run or loop isn't run or a function isn't called, but all root imports/includes will 100% be checked.

So what? Test cases run all code (I guess). Imports in functions or ifs are fine.

[Andrew15-5]

So what? Test cases run all code (I guess). Imports in functions or ifs are fine.

Then we are golden (good to go). If you run your regular tests after applying relative paths and before publishing the package, then no additional tests are necessary.