forcedotcom / salesforcedx-vscode

Salesforce Extensions for VS Code
https://developer.salesforce.com/tools/vscode
BSD 3-Clause "New" or "Revised" License
954 stars 406 forks source link

Issue with VSCode Conflict Detection for Salesforce LWCs #4765

Closed jlnatarajan closed 1 year ago

jlnatarajan commented 1 year ago

Summary:

Conflicts are not being detected as expected for Lightning Web Components (LWCs) during VSCode conflict detection.

Steps To Reproduce:

  1. Video attached: https://user-images.githubusercontent.com/85702580/228947617-76352ca0-14bd-469b-9296-ca6f8d15ca2a.mov

Expected result:

Conflict detected when test is run.

Actual result:

No conflict detection messages displayed.

Additional information: please see video above

VS Code: Version: 1.76.2 (Universal) Commit: ee2b180d582a7f601fa6ecfdad8d9fd269ab1884 Date: 2023-03-14T17:54:09.061Z (1 wk ago) Electron: 19.1.11 Chromium: 102.0.5005.196 Node.js: 16.14.2 V8: 10.2.154.26-electron.0 OS: Darwin arm64 21.6.0 Sandboxed: No Salesforce CLI: sfdx-cli/7.193.2 darwin-x64 node-v18.14.2

randi274 commented 1 year ago

Related info for trust or @AnanyaJha : https://sfdc.co/testConflictThread

randi274 commented 1 year ago

Hey @jlnatarajan - is this actually an issue with Apex Triggers (or other metadata than LWCs not working correctly with conflict detection)? What I see in the attached video is:

I have seen this issue before, but not consistently, and am unable to reproduce it today. We also recently made a number of changes to our deploy/retrieve logic - can you retest and see if that's still an issue for you?

github-actions[bot] commented 1 year ago

This issue has not received a response in 7 days. It will auto-close in 7 days unless a response is posted.