-
Notifications
You must be signed in to change notification settings - Fork 352
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 Support #205
Comments
Hey @Manuelandro I have interest in TS too, link here your progress i think i could help. |
He @Manuelandro @kamikazebr - any word on progress here? 😁 |
Is anybody actively developing on this? I've started work on migrating the template over to TypeScript. |
@nukemandan @tarrball I had hope @Manuelandro already had some WIP on that, but not got awnser, I have some time to help but not to start of migration. So @tarrball if you need some sporadic help on that i'll happy support. |
@kamikazebr I've got the template working with TypeScript, with some package warnings & eslint removed, so there's some work to be done still. I've got the repo forked here to work on it. I'm not sure if that's the best or desired way for me to proceed with development for the greater good, but it's how I started it for myself. |
Hey @tarrball i saw some commits there, amazing! Yah i think fork is way to go working on one branch to PR later. I never worked on fork-fork project, but i have almost sure i just need add new remote, and make amends if necessary on your branch. About the workflow, i think part will run on Issue on your fork and linked here on that. What you think need be done there yet? I'll fetch and run on my local |
@nukemandan @tarrball i had tested and run the code, its look great. Should create some branch and PR to merge here? |
I dropped eslint, since it was having build issues (related to webpack in some way, I think), so that's one issue. There are couple other minor things (like having to hard code the color in the transaction button component) that I hastily did to get things building. Other than that, other questions/concerns I have are: I don't know how this fits in with the current repo. Is there a desire to replace what's in place with a TypeScript solution, or is there a desire to maintain both? Are there any code snippers or tutorials that would need to be updated to note the changes? |
I've got this working fully now without any issues. |
cool @tarrball ! 😁 |
@kamikazebr @nukemandan PR opened -> #223 |
Made some enhancements to this PR here --> tarrball#1 |
I've made good progress on this and kept current with the It's not trivial to rebase each time there are significant change on |
@tarrball are you working on this issue still? I wanna jump to help. Let get it done? @nukemandan may help to solve it as I wanna help Tarrball to follow it. |
@langdon0003 no I haven't done anything on this since my last comment, but it doesn't seem like much has changed in this repo since then, so it seems like it's stable enough to make the switch to TS. As long as there is enough buy-in and a good definition of "done" to work toward (as mentioned a few months ago). |
I am currently checking on this repo [email protected]:tarrball/substrate-front-end-template.git at "ts/main" branch but It look like still have done yet. Am I checkout right repo? Could you update the latest and work one? Thank you so much! |
@langdon0003 the last time I rebased, it was into this branch https://github.com/tarrball/substrate-front-end-template/tree/ts-again. I got pretty far into it but it's been silent for a while so I haven't messed with it since |
@tarrball Does your last version work? I can't really get the version running from the https://github.com/tarrball/substrate-front-end-template/tree/ts-again and from this repository for Typescript. |
Is it something that could interest you? I think i'm gonna implement it on my clone for personal use, but if you'd like I could open a pull request
The text was updated successfully, but these errors were encountered: