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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Typescript broken with mobx state tree #2668

Open
vantuan88291 opened this issue Apr 18, 2024 · 3 comments
Open

Typescript broken with mobx state tree #2668

vantuan88291 opened this issue Apr 18, 2024 · 3 comments
Labels

Comments

@vantuan88291
Copy link
Contributor

Describe the bug

I dont know why ts always got error like this:
Screenshot 2024-04-18 at 20 10 20
Still work as normal but ts broken, please help

Ignite version

9.6.3

Additional info

System
platform darwin
arch arm64
cpu 8 cores Apple M1 Pro
directory paradise /Users/vantuan88291/code/reactnative/paradise

JavaScript (and globally-installed packages)
node 18.17.1 /opt/homebrew/opt/node@18/bin/node
npm 9.6.7 /opt/homebrew/opt/node@18/bin/npm
appcenter-cli 2.14.0
code-push-cli 3.0.0
corepack 0.18.0
eas-cli 0.59.0
expo-cli 6.0.1
npm 9.6.7
yarn 1.22.18
yarn 1.22.22 /Users/vantuan88291/code/reactnative/paradise/node_modules/.bin/yarn
ignite-cli 8.8.7
pnpm - not installed
bun - not installed
expo 50.0.15 managed
expo global cli 6.0.1 Deprecated: Found 'expo-cli' installed. Please remove it.

Ignite
ignite-cli 9.6.3 /Users/vantuan88291/.npm/_npx/e31027f3785124a8/node_modules/.bin/ignite
ignite src build /Users/vantuan88291/.npm/_npx/e31027f3785124a8/node_modules/ignite-cli/build

Android
java 17.0.9 /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
android home - /Users/vantuan88291/Library/Android/sdk

iOS
xcode 15.1
cocoapods 1.13.0 /Users/vantuan88291/.rvm/gems/ruby-3.0.0/bin/pod

Tools
git git version 2.39.1 /opt/homebrew/bin/git

@frankcalise
Copy link
Contributor

frankcalise commented May 6, 2024

Hi @vantuan88291 can you provide your TypeScript version installed and share what the error is?

I'm assuming withSetPropAction it is imported at the top of your file?

@frankcalise
Copy link
Contributor

@coolsoftwaretyler does this ring any bells? I know it isn't much to go off of, but figured I'd ask

@coolsoftwaretyler
Copy link
Contributor

Nothing really jumps out to me. I don't often use the separate props builder call, but I don't see an issue there. Here's a (non-reproducing) reproduction: https://codesandbox.io/p/sandbox/ignite-2668-mg594q?file=%2Fsrc%2Findex.ts%3A16%2C1

I'm using the withSetPropAction from the recipe article, in which I changed some of the TypeScript. But I also do not see an issue when I switch over to Ignite's version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants