Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@YUUU23
Copy link
Contributor

@YUUU23 YUUU23 commented Jul 12, 2024

  • Add mock binding when user clicks continue anyway
  • Change log.info to not include port
  • CONTINUE_ANYWAY throws warning that it's never used after deleting check on if continue anyway is true, we return from handleEventSend(); I'm not sure if we can remove this variable entirely? Otherwise to resolve this, I added a check for that if it's CONTINUE_ANYWAY is false, we then set it to true

@YUUU23 YUUU23 changed the base branch from main to feat-v3.4.1 July 12, 2024 04:16
@YUUU23 YUUU23 self-assigned this Jul 12, 2024
@github-actions
Copy link

github-actions bot commented Jul 12, 2024

Visit the preview URL for this PR (updated for commit ef8e5ed):

https://ccv-honeycomb--pr510-add-mockbind-4eu58dfx.web.app

(expires Fri, 19 Jul 2024 16:58:01 GMT)

🔥 via Firebase Hosting GitHub Action 🌎

Sign: 4ace1dcea913a952d2a1af84b94a4421bf36e610

@YUUU23 YUUU23 requested a review from RobertGemmaJr July 12, 2024 04:21
@YUUU23 YUUU23 added the 3.4 Versioning: Issue in regards to version 3.4 release label Jul 12, 2024
Comment on lines 419 to 421
if (CONTINUE_ANYWAY == false) {
CONTINUE_ANYWAY = true;
}
Copy link
Contributor

Choose a reason for hiding this comment

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

I believe this can be simplified without the if statement

Suggested change
if (CONTINUE_ANYWAY == false) {
CONTINUE_ANYWAY = true;
}
CONTINUE_ANYWAY = true;

Copy link
Contributor

Choose a reason for hiding this comment

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

Is this mainly a statement to use the CONTINUE_ANYWAY variable?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I agree this is very redundant -- yes, it is primarily to use this variable to pass the eslint tests. I was wondering since it gives this unused variable warning, would it be okay to just delete this variable overall?

Copy link
Member

Choose a reason for hiding this comment

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

We can safely remove the variable! That variable was only there to skip sending data to a port that didn't exist, but now we have a mock port to send it to

Copy link
Member

@RobertGemmaJr RobertGemmaJr left a comment

Choose a reason for hiding this comment

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

This looks fantastic! Adding the mock port has been a much needed addition for quite some time now. Thank you for tackling it!

You can safely remove the CONTINUE_ANYWAY variable, then this is ready to go

@YUUU23 YUUU23 requested a review from RobertGemmaJr July 12, 2024 16:56
@YUUU23
Copy link
Contributor Author

YUUU23 commented Jul 12, 2024

This looks fantastic! Adding the mock port has been a much needed addition for quite some time now. Thank you for tackling it!

You can safely remove the CONTINUE_ANYWAY variable, then this is ready to go

This variable should be removed!

Copy link
Member

@RobertGemmaJr RobertGemmaJr left a comment

Choose a reason for hiding this comment

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

Wonderful!

@YUUU23 YUUU23 merged commit c008e64 into feat-v3.4.1 Jul 12, 2024
@YUUU23 YUUU23 deleted the add-mockbind branch July 12, 2024 17:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

3.4 Versioning: Issue in regards to version 3.4 release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Serial point connection with MockBindings when running in CONTUNUE_ANYWAY mode

4 participants