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

Migrating lib/utils/debuggability.js file to Typescript. #3880

Closed

Conversation

yashPratp983
Copy link
Contributor

No description provided.

@yashPratp983 yashPratp983 changed the title Migratint lib/utils/debuggability.js file to Typescript. Migrating lib/utils/debuggability.js file to Typescript. Aug 16, 2023
@github-actions
Copy link

Status

  • ❌ No modified files found in the types directory.
    Please make sure to include types for any changes you have made. Thank you!.

Copy link
Member

@vaibhavsingh97 vaibhavsingh97 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I recommend using Private Class Members features of Javascript
Ref: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes/Private_class_fields

Comment on lines 2 to 3
private static _debugMode: boolean;
private static _stepOverAndPause: boolean;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
private static _debugMode: boolean;
private static _stepOverAndPause: boolean;
static #debugMode: boolean = false;
static #stepOverAndPause: boolean = false;

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we should avoid changing the functionality of the code while annotating. So, while changing to # notation seems fine to me here, we should avoid initializing them with false, which will definitely impact the functionality of the transpiled JS code.

@beatfactor beatfactor closed this Nov 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants