Conversation
| @@ -1,11 +1,11 @@ | |||
| { | |||
There was a problem hiding this comment.
What: The package name change from @bsf/force-ui to @brainstormforce/force-ui should be validated across the codebase.
Why: Changing the package name can lead to potential issues if any part of the codebase still references the old name. It's crucial to ensure that all references are updated to prevent any runtime errors or missing module issues.
How: Search the entire codebase for @bsf/force-ui to ensure that it's replaced with @brainstormforce/force-ui in all relevant files, including import statements.
| "version": "1.7.8", | ||
| "lockfileVersion": 3, | ||
| "requires": true, | ||
| "packages": { |
There was a problem hiding this comment.
What: Ensure that the versioning strategy reflects project requirements.
Why: The versioning strategy in package-lock files is important for maintaining consistency across installations and deployments. Ensure that this version number aligns with the semantic versioning strategy that is being used throughout the project.
How: Consider establishing a policy for versioning that includes major, minor, and patch changes to maintain clarity on updates.
Description
Screenshots | Video with voice-over
Link to Figma (If applicable)
How has this been tested?
Checklist: