You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For new projects, there is no need to show the warning about the dependency update. This behavior is correct in the CLI build but the warning is shown in LS.
Steps to Reproduce
Create a new package and open it is VSCode
Execute bal build in the VSCode terminal Observation: The dependency update warning is shown in the Problems tab
Open the Dependencies.toml Observation: The warning goes away
Expected behavior:
The warning should not be shown at all for a new package
Affected Version(s)
2201.5.0 and above
OS, DB, other environment details and versions
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response
The text was updated successfully, but these errors were encountered:
This issue is NOT closed with a proper Reason/ label. Make sure to add proper reason label before closing. Please add or leave a comment with the proper reason label now.
- Reason/EngineeringMistake - The issue occurred due to a mistake made in the past. - Reason/Regression - The issue has introduced a regression. - Reason/MultipleComponentInteraction - Issue occured due to interactions in multiple components. - Reason/Complex - Issue occurred due to complex scenario. - Reason/Invalid - Issue is invalid. - Reason/Other - None of the above cases.
Description
For new projects, there is no need to show the warning about the dependency update. This behavior is correct in the CLI build but the warning is shown in LS.
Steps to Reproduce
Observation: The dependency update warning is shown in the
Problems
tabObservation: The warning goes away
Expected behavior:
The warning should not be shown at all for a new package
Affected Version(s)
2201.5.0 and above
OS, DB, other environment details and versions
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response
The text was updated successfully, but these errors were encountered: