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 Support #205

Open
Manuelandro opened this issue Oct 10, 2021 · 18 comments
Open

Typescript Support #205

Manuelandro opened this issue Oct 10, 2021 · 18 comments
Assignees
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@Manuelandro
Copy link
Contributor

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

@kamikazebr
Copy link

Hey @Manuelandro I have interest in TS too, link here your progress i think i could help.

@nuke-web3 nuke-web3 added good first issue Good for newcomers help wanted Extra attention is needed labels Oct 20, 2021
@nuke-web3
Copy link
Contributor

He @Manuelandro @kamikazebr - any word on progress here? 😁

@tarrball
Copy link

tarrball commented Dec 16, 2021

Is anybody actively developing on this? I've started work on migrating the template over to TypeScript.

@kamikazebr
Copy link

@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.

@tarrball
Copy link

tarrball commented Dec 17, 2021

@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.

@kamikazebr
Copy link

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

@kamikazebr
Copy link

@nukemandan @tarrball i had tested and run the code, its look great. Should create some branch and PR to merge here?

@tarrball
Copy link

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?

@tarrball
Copy link

I've got this working fully now without any issues.

@nuke-web3
Copy link
Contributor

cool @tarrball ! 😁
.... maybe a PR here?
I think we could maintain an alt branch of this with your support that is pure TS... or with the maintainers buy-in, move to this over js.

@tarrball
Copy link

@kamikazebr @nukemandan PR opened -> #223

@fuzzc0re
Copy link

fuzzc0re commented Jan 6, 2022

Made some enhancements to this PR here --> tarrball#1
Hope this will bring us closer to a strongly typed template.
Cheers.

@tarrball
Copy link

tarrball commented Feb 23, 2022

I've made good progress on this and kept current with the main branch on my own fork, but I'm not sure how far to go with the typings. Do we want to create typings that match all the pallets/RPC's in the main branch? I think avoiding all "any" types is going to be tough.

It's not trivial to rebase each time there are significant change on main, so I'm just wondering what the definition of "done" is on this issue?

@langdon0003
Copy link

@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.

@tarrball
Copy link

tarrball commented Jun 8, 2022

@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).

@langdon0003
Copy link

@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 git@github.com: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!

@tarrball
Copy link

@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

@Chralt98
Copy link

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

7 participants