microsoft / microsoft/typespec

[Bug]: Enum member integer value less than `-Number.MAX_VALUE` or greater than `Number.MAX_VALUE` becomes `-Infinity` or `Infinity`, respectively

Open
#5,296 1 comment 0 reactions 0 assignees View on GitHub
design:needed needs-area triaged:core
Dominant language
Java
Stars
5.9k
Forks
394
Avg merge
1d 23h
Merged PRs (30d)
104

Description

### Describe the bug

I guess maybe I would expect the enum member's `value` property to return `string | number | bigint` in the current state, and in this case it would become a `bigint`? Probably better to figure out https://github.com/microsoft/typespec/issues/3314 though

### Reproduction

[Playground Link](https://typespec.io/playground/?c=CmVudW0gTnVtYmVyRcQLewogIE1lxA86IDQw3wHfAd8B3wHfAd8B3wHfAd8B3gEsCn0K&e=%40typespec%2Fopenapi3&options=%7B%7D)

### Checklist

- [x] Follow our [Code of Conduct](https://github.com/microsoft/typespec/blob/main/CODE_OF_CONDUCT.md)
- [x] Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
- [x] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/Microsoft/typespec/discussions).
- [x] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.