stefanprobst

### Describe the bug Pressing the Ins key will print the literal `undefined` (as does any F1–F12 not handled by the OS) ### To Reproduce 1. Press Ins 2. Input...

`UnhandledSchemeError` when dependency uses `node:assert` imports

21

### What version of Next.js are you using? 11.1.2 ### What version of Node.js are you using? 14.17.6 ### What browser are you using? ff ### What operating system are...

Focus not trapped in detached mode

2

## Description when in detached mode (fullscreen or modal), focus should be trapped. ## Reproduction **Steps** 1. Go to https://www.algolia.com/doc/ui-libraries/autocomplete/introduction/what-is-autocomplete/ 2. Reduce viewport width to 500px to switch to detached...

Navigating options should not scroll page

3

## Description When navigating options in the combobox popup, the scroll position on the page should not change. ## Reproduction **Steps** 1. Go to https://www.algolia.com/doc/ui-libraries/autocomplete/introduction/what-is-autocomplete/ and place cursor in the...

When selecting a Menu item, element behind popup receives pointer event

25

# 🐛 Bug Report When a `Menu` item is selected on a touch device, interactive elements *behind* the menu popup receive the pointer event as well. ## 🤔 Expected Behavior...

**What**: support providing input `source` as `Vfile` with full `path`, which can be accessed by plugins on `vfile.path` **Why**: being able to pass input to a `unified` pipeline as `VFile`...

getFieldTC should return temporary composers

2

Recently, `getFieldTC` methods were changed from `schemaComposer.createTempTC` to `schemaComposer.createTC`. Was that on purpose?

Noop tests

2

These two tests seem to be left over from an earlier version? https://github.com/graphql-compose/graphql-compose/blob/05f69f12ad05051360dd808440314114a879b17d/src/__tests__/TypeComposer-test.js#L95 https://github.com/graphql-compose/graphql-compose/blob/05f69f12ad05051360dd808440314114a879b17d/src/__tests__/InterfaceTypeComposer-test.js#L94

required and readyOnly/writeOnly properties

4

hi, i'm curious how this library handles the contextual behavior of `required` properties interacting with `readOnly`/`writeOnly`? from [https://swagger.io/specification](https://swagger.io/specification/#fixed-fields-20) - "If the property is marked as readOnly being true and is...

fix: check declaration

1

Issue: # ## What Changed i was getting crashes in vs code without this check. if you want you could also enable the typescript `noUncheckedIndexedAccess` option to more easily catch...