janpio
Follow
Create your own GitHub profile
Sign up for your own profile on GitHub, the best place to host code, manage projects, and build software alongside 50 million developers.
Sign up
Pinned
2,256 contributions in the last year
Activity overview
Contribution activity
August 2020
- janpio/sql-load-test Rust
- janpio/Bedrock C
- janpio/vscode-graphql TypeScript
Created a pull request in prisma/prisma-labelsync that received 27 comments
Created an issue in prisma/prisma that received 7 comments
Nicer error message for schema with missing data source
Internal context: https://prisma-company.slack.com/archives/C4GCG53BP/p1597674794047900
Schemas now require a datasource for generate, otherwise yo…
7
comments
- [Introspection] Partial Unique Index (Postgres) are introspected as normal unique indexes
- `We can't release, as the e2e tests are not passing for the ${tag} npm tag!` logic should also check if tested version = version that should be promoted to release
- `We can't release, as the e2e tests are not passing for the ${tag} npm tag!` checks wrong npm tag for passing e2e tests when promoting a patch-dev to latest
- Using `env` as datasource `provider` leads to ugly error message
- Re-Introspection does not output list of fields that `cuid()` was applied to
- Stabilize Re-Introspection and integrate it into normal `introspect`
- Connection URL error message shows wrong snippet when using `url` in PrismaClient constructor
- Error: [libs\datamodel\core\src\dml\datamodel.rs:166:9] Every RelationInfo should have a complementary RelationInfo on the opposite relation field.
- Throw better error message when env function doesn't receive a string ie `env(FOO)` instead of `env("FOO")`
- Throw better error message when single quotes are used for properties inside datasource or generator blocks
- SQLite: Use WAL mode
- "Error state" CLI output should always include CLI version
- `generate`: `--postinstall` that gets `npm` command as parameter
- Invalid or erroring commands do not trigger update check
- Collect `dbgenerated()` values in an issue via "warning" output in Introspection
- Investigate ProxySQL as a PgBouncer for MySQL alternative
- Minimize list of reserved words for usage as model names
- Remove GraphQL related reserved words
- `Transaction` is still a reserved word in 2.4.1
- Support indexes using expressions (MySQL 8.0.13+)
- Output Studio package version in `prisma -v`
- Dependency updates: Run only tests for projects that were updated
- Missing files and versions
- Lower the number of pushes from Renovate and Dependabot
- Do not run `Lint PR` workflow on automated PRs
- Do not start/queue another `check-for-update` run if there are already some waiting
- Input 'version' has been deprecated with message: The version property will not be supported after October 1, 2019. Use node-version instead