Sebastian Nemeth

No types from package...?

5

Hey man, nice idea using typescript to manipulate karabiner! I haven't really played with Deno so I'm not sure if I'm doing something wrong or if its a bug on...

Currently, for mutations, when the debounce timeout is reached and a request is sent, if the the same request is queued again while the first's request is in network flight,...

[v2] isValid=true on mount, even though initialValues are invalid and validateOnMount=true

50

## 🐛 Bug report ### Current Behavior isValid is true once the form mounts, even though the validationSchema invalidates initialValues and the form is untouched. ### Expected behavior isValid prop...

Hey man! Great work on this plugin, smooths over so much codegen pain. I'm having an issue where I'm using a `with-typescript-graphql` setup on `nextjs`. I'm using `getStaticProps` and so...

node_patches.js causes Error [ERR_REQUIRE_ESM] when package.json is type="module"

2

# 🐞 bug report ### Affected Rule The issue is caused by the rule: `nodejs_binary` - specifically, the underlying auto generated rule from `load("@npm//:index.bzl", ...)` ### Is this a regression?...

language rules not applied in *.svelte script blocks?

10

Hi, I'm probably misunderstanding how this plugin is supposed to work. I was expecting that the rules that are applied for vanilla `*.ts` files should also be applies in `*.svelte`...

Node objects & node ids are not re-used in unchanged sub-trees when editing.

3

I'm trying to figure out incremental parsing with a related Discussions thread: https://github.com/tree-sitter/tree-sitter/discussions/1964 My goal is to be able to compare the CSTs before and after the edit, to figure...

Improve type readability (fix type alias propagation, allow aliasing inferred types)

7

# Suggestion ## 🔍 Search Terms preserve type aliases,inferred types,type names,readability,type expansion ## ✅ Viability Checklist My suggestion meets these guidelines: * [*] This wouldn't be a breaking change in...

We're experiencing a problem using `isomorphic-unfetch` in `storybook` together with `nextjs`. Even though it works fine in the `next` build, importing `isomorphic-unfetch` in a component in `storybook` causes several errors....

ignore branches whose names aren't semver compatible, instead of throwing error

4

## New feature motivation I am setting up `semantic-release` to deploy any non support/master/next branch as a pre-release branch. My branch configuration appends: ``` { name: '*', prerelease: true }...