Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Type Name Conflict with Native JS Api #251

Open
xianshenglu opened this issue Aug 26, 2021 · 0 comments
Open

Type Name Conflict with Native JS Api #251

xianshenglu opened this issue Aug 26, 2021 · 0 comments

Comments

@xianshenglu
Copy link

馃崺 Feature Request

Is your feature request related to a problem?

Say my original code is

console.log(Object.keys({error:false})) // 'error:false'

then I add other codes like

+ import {Object} from "ts-toolbelt"
console.log(Object.keys({x:1}))
+ type ApiResponse<T extends object> = Object.Merge<{error: boolean}, T>

Then the app breaks down because of the name conflict.

Describe the solution you'd like

Remove the name conflict. For example Object.Merge to Merge or ObjectMerge?
Or at least tell the users like MUST run tsc first before the build script?

@xianshenglu xianshenglu changed the title Name Conflict with native JS Api Name Conflict with Native JS Api Aug 26, 2021
@xianshenglu xianshenglu changed the title Name Conflict with Native JS Api Type Name Conflict with Native JS Api Aug 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant