-
Notifications
You must be signed in to change notification settings - Fork 46
Fix test --coverage errors related to TS #8
Fix test --coverage errors related to TS #8
Conversation
…tion-core into feature/typescript Conflicts: package.json yarn.lock
ok I need a little help here. not getting too much progress :( it is strange that in the circleci log we are getting the typescript help text and not locally? if someone with more experience with circleci can help that would be great!. I'm sure is a really silly (and funny) error... |
i noticed this: https://github.com/react-navigation/react-navigation-core/blob/master/.circleci/config.yml#L5 maybe using node 7 is causing any problem? I'm using 9.4.0 locally.. |
package.json
Outdated
}, | ||
"peerDependencies": { | ||
"react": "*" | ||
}, | ||
"jest": { | ||
"preset": "react-native", | ||
"testRegex": "/__tests__/[^/]+-test\\.js$", | ||
"testRegex": "/__tests__/[^/]+-test\\.[jt]sx?$", |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
"tsConfig": "./tsconfig.test.json", | ||
"diagnostics": { | ||
"ignoreCodes": [ | ||
151001 |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
.gitignore
Outdated
|
||
# TypeScript-generated files | ||
*.d.ts | ||
!src/react-navigation.d.ts |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
ok everything solved :) |
.gitignore
Outdated
|
||
# TypeScript-generated files | ||
*.d.ts | ||
!src/react-navigation.d.ts |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry, something went wrong.
Conflicts: example/App.js example/src/SimpleStack.js src/getChildEventSubscriber.ts
Finally, because of some updates to sorry for the mess with this PR, I need to properly setup my machine to be more reliable with the CI, a lot of trials and errors. or maybe I can learn a better way to maintain this contributions cleaner? hope this now can be approved :) |
@horacioh you forgot to fix this buggy regex: #8 (comment) |
@horacioh - can you open a followup pr for that? thx 🙏 |
I can't get the example project running with typescript :( here's my attempt: https://github.com/react-navigation/react-navigation-core/tree/%40brent/attempted-example-fix-ts |
checking it now @brentvatne |
@brentvatne I got the example project working in your branch: let me dig dipper into why this two packages are not installed as a dependency in the example project. maybe because the |
Sorry I had to revert this change because I needed to get examples running again: 1897b32
Let me know if this is the problem and I can make a release of /native without it. Its funny how our real devDependencies seem to be the dependencies of the example project |
I think this is the problem. I manually add it as a dependency and it was working correctly. so if you add hope this helps :) |
@ericvicenti do you want me to do a PR of this? |
@horacioh - yeah that would be great! thanks |
is the example working in master? its not for me. I tried to link the local packages to test my changes before pushing any change and now i got other errors :( trying to resolve this issues before submitting another PR. sorry! |
hey @horacioh - it's running for me on master. |
hey @brentvatne ! |
also I took out all the pre-commit/format config from this branch. I think the best way is to fix this in another PR.