Bug report ยท Feature request ยท Read Docs
I'm a GIS beginner, please let me know if you see anything problematic in the way this library is implemented. The library is also missing support for very many functions. PRs are very welcome, all I ask is that you add test coverage for any new functions :)
pnpm add drizzle-postgis
Patching drizzle-kit (See Troubleshooting for more info) is no longer required in most cases (unless you need to generate migrations with a box2d type).
If you're having trouble with Postgres complaining that the functions can't be found, try using config.setPostGISSchema("<schema>")
There's more information about how to use these functions here: https://postgis.net/docs/reference.html
Unfortunately drizzle-kit has a bug that causes some custom types to be quoted. The only type in this library that is still affected (as of drizzle-kit 0.22.0) is
box2d
. In order to use this with migrations, you need to apply a patch (see below). This issue tracks this problem somewhat: https://github.com/drizzle-team/drizzle-kit-mirror/issues/350
The patch file is located in repository under the patches
directory: patches/drizzle-kit@<version>.patch
. (Replace
You can copy the patch file content directly from the repository to your local patches directory.
If you're using pnpm, you can apply the patch by adding the following lines to your package.json
file under the pnpm
section:
"pnpm": {
"patchedDependencies": {
"drizzle-kit@<version>": "patches/drizzle-kit@<version>.patch"
}
}
This configuration tells pnpm to apply the specified patch to the drizzle-kit@<version>
dependency.
Note that patches/drizzle-kit@<version>.patch
is the path to the patch file
After updating your package.json
, run pnpm install
to install the patched dependency.
If you prefer not to modify your package.json
, you can manually apply the patch using the patch
command:
drizzle-kit.patch
.drizzle-kit
is installed (usually node_modules/drizzle-kit
).patch -p1 < /path/to/drizzle-kit.patch
This will apply the patch to the drizzle-kit
dependency.
The project is configured to auto-generate the documentation using typedoc. The documentation is generated in the docs
folder.
The documentation will get generated when the code is pushed to the main
branch. You can also generate the documentation locally by running the command pnpm run build:docs
.
Please make sure to follow the conventional commit messages format while making changes. This helps in generating changelogs and versioning the package.
Generated using TypeDoc