Skip to content
This repository has been archived by the owner on Jan 29, 2024. It is now read-only.

Weird bugs from TypeScript (to avoid in Hegel) #313

Open
trusktr opened this issue Sep 13, 2020 · 3 comments
Open

Weird bugs from TypeScript (to avoid in Hegel) #313

trusktr opened this issue Sep 13, 2020 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@trusktr
Copy link

trusktr commented Sep 13, 2020

I thought I would place this here. This makes no sense to an end user experiencing the error: microsoft/TypeScript#18877

I'm not sure if Hegel will support augmentation of existing types (which is valid JavaScript use case), but if so, this would be an issue to avoid.

Btw, is there a Hegel chat server? Might be easier to chat about these things in chat before opening an issue. :)

@JSMonk JSMonk added the enhancement New feature or request label Sep 17, 2020
@hinell
Copy link

hinell commented Nov 13, 2020

There is a lot of bugs, quirks and useless things you want to avoid from TS lol. 😉 The first step is to avoid using TS first.

@trusktr
Copy link
Author

trusktr commented Jan 18, 2021

There is a lot of bugs, quirks and useless things you want to avoid from TS lol.

Yeah. I really dislike this one lately:

playground

And the GitHub issue which is closed and labeled "working as intended".

@trusktr trusktr changed the title Weird bug from TypeScript (to avoid in Hegel) Weird bugs from TypeScript (to avoid in Hegel) Jan 18, 2021
@trusktr
Copy link
Author

trusktr commented Jan 18, 2021

All the issues in here really bug me too: microsoft/TypeScript#35822

We can make this issue a list of all the things not to do from TS.

@JSMonk JSMonk self-assigned this Jan 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants