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

feat: fixes Apex Interactive Debugger #4980

Merged
merged 4 commits into from
Jul 18, 2023

Conversation

RitamAgrawal
Copy link
Member

What does this PR do?

This PR updates two environment variables from sfdx to sf style.

  • SFDX_INSTANCE_URL ▶️ SF_ORG_INSTANCE_URL
  • SFDX_DEFAULTUSERNAME ▶️ SF_TARGET_ORG

This removes the warning we are receiving while launching the apex interactive debugger. Now launches the apex debugger successfully.

What issues does this PR fix or reference?

#4927, @W-13757531@

Functionality Before

image (1)

Functionality After

No warnings!

@RitamAgrawal RitamAgrawal requested a review from a team as a code owner July 14, 2023 22:37
Copy link
Contributor

@CristiCanizales CristiCanizales left a comment

Choose a reason for hiding this comment

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

I verified the warnings are not showing up anymore thus there's no related error ✅
image
:shipit:

@supert3d
Copy link

Awesome. Thanks for your work on this everyone!

@RitamAgrawal RitamAgrawal requested review from CristiCanizales and a team July 17, 2023 18:01
@RitamAgrawal
Copy link
Member Author

@supert3d It would be great if you can validate the same on your org. You can use the vsixes of the test run for validation.

@RitamAgrawal RitamAgrawal merged commit 581949d into develop Jul 18, 2023
16 checks passed
@RitamAgrawal RitamAgrawal deleted the ra/upgrade_sfdx_sf_style_env branch July 18, 2023 01:38
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.

Unable to use VSCode Apex Debugger. Suspect the issue is due to recent migration from SFDX to SF
3 participants