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

Update "Fix a bug" section of the Onboarding Bootcamp #2585

Open
yyccbb opened this issue Jan 19, 2025 · 2 comments
Open

Update "Fix a bug" section of the Onboarding Bootcamp #2585

yyccbb opened this issue Jan 19, 2025 · 2 comments

Comments

@yyccbb
Copy link

yyccbb commented Jan 19, 2025

Please confirm that you have searched existing issues in the repo

Yes, I have searched the existing issues

Any related issues?

No response

Tell us about your environment

Windows 11, MacOS Sequoia

MarkBind version

Not relevant

Describe the bug and the steps to reproduce it

I was following the instructions under DG --> Onboarding Bootcamp --> Fix a bug and the markbind command would stop working after running git checkout to roll back to a buggy version of the codebase (as stated in the instructions). I suspect that some dependencies are broken by rolling back.

under Windows 11 under MacOS Sequoia
Image Image

Note: npm run setup fails under both environments. (lerna ERR! npm install exited 7 in 'root')

Expected behavior

No response

Anything else?

Let's probably update the "Fix a bug" section so that a more recent bug that does not lead to broken dependencies can be used as practice material.

@lhw-1
Copy link
Contributor

lhw-1 commented Jan 19, 2025

It should be sufficient to update the documentations with a branch of MarkBind that is recent enough, but still has an outstanding bug (or we can create a branch for this purpose if needed).

@lhw-1 lhw-1 added the d.easy label Jan 19, 2025
@Incogdino
Copy link
Contributor

Incogdino commented Jan 21, 2025

I also want to add that there is a minor documentation link issue at the end of the "Migrating to TypeScript" page where it links to the Project Structure instead of "Migrating Node.js". Would perhaps be good if this can be updated alongside the documentation as well.

Image

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

No branches or pull requests

3 participants