Derk-Jan Karrenbeld
Derk-Jan Karrenbeld
@AndresCampuzano Can you post your solution please? Along with the solution, can you also post the files you have locally (`ls` output should suffice) and the contents for the test...
I did the following and it worked 1. login with github 2. go to settings 3. find my account email 4. logout 5. press sign in 6. press forgot password...
@rwp0 @divasriv can you both share your Exercism username? Then we can ask @iHiD to do some magic.
@SichangHe please share your Exercism username here.
Especially that first link will help. In the meanwhile, I'll guess we'll amend the runner to block on TS errors.
That example code editor looks cool and seems to also include auto complete. Definitely worth checking out.
Locally I have tsc running, as well as adding tests that test the definitions generated instead of just the compiled JavaScript. However, for usage we do really need the LSP...
I don't know how the current UI works, but basically you want the _url_ to be the _single source of truth_. So changing the dropdown / typing something / whatevs...
It should be. When its not, it means that the elements that use the state are not using the url state as ground truth 😁
I think I have an example of this in my hiring-example repository, where I fetch the url state / query param on mount, and use that to "hydrate" the query.