-
### Requirements
I was just examining the API to look at adopting a feature-flagging standard and surprised to find that after defining a strict set of variants, there is no Typescript compiler error…
-
There are some patterns that lead to degraded type-safety.
We should review our codebase, especially things added in electra, for these types of patterns and refactor if possible.
Ideally we can m…
-
Need to provide better type safety in:
- [x] Smithy specification
- [x] [Domain](https://github.com/lenguyenthanh/fide/blob/main/modules/domain/src/main/scala/Domain.scala)
- [ ] [Config](https:/…
-
WARNING: Brain dump ahead!
Today, `build_int_add` looks approximately like `build_int_add(&self, left: &IntValue, right: &IntValue) -> IntValue`. This is great, because it'll stop you from trying t…
-
Throughout the project, there are lots of references to "string". This is great for a quick start, but leads to possible mistakes.
For example a `Hash` has the same type as a `PrivateKey`, even if th…
luxbe updated
2 months ago
-
Dealing with interfaces can be quite burdensome. Why not add type safety to the project?
The data matched by a single character matcher type `byte`, and if you are matching multiple items it's alwa…
-
### Description / Reproduction
The following ought to generate a type-error where `whoops` is declared, but instead it complies and violates type safety, interpreting memory as incorrect type.
```…
-
#1544 bumped the version of Prisma from 4.12 to 4.16.
This change introduced a regression in our full-stack type safety DX. The functionality is still there, but type names are far less ergonomic.
…
sodic updated
4 weeks ago
-
### Describe the feature
The current API lacks type safety because the session defaults to an empty object, which is not properly handled in the implementation. To improve type safety, I recommend th…
-
having schema set like this
```
export const schema = {
response: {
201: z.object({
status: z.literal('success'),
data: z.object({
id: z.numb…