-
Notifications
You must be signed in to change notification settings - Fork 25
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
BIT-1212: Nested Folder Support #532
Conversation
Bitwarden code coverageTotal coverage:
|
File | Coverage |
---|---|
BitwardenShared/Core/Platform/Utilities/Tree.swift | 100.00% |
BitwardenShared/Core/Vault/Extensions/BitwardenSdk+Vault.swift | 62.37% |
BitwardenShared/Core/Vault/Repositories/VaultRepository.swift | 96.57% |
BitwardenShared/UI/Vault/Vault/VaultList/VaultListGroup.swift | 98.33% |
Powered by Slather
Generated by 🚫 Danger
/// - Returns: A list of items for the group in the vault list. | ||
/// | ||
private func vaultListItems( | ||
private func vaultListItems( // swiftlint:disable:this function_body_length |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎨 : Instead of disabling the swiftlint warning on length here, would it be possible to put some of the functionality into a separate private method, and make this smaller as a result? In particular, could the calculation of folderSection
be split out?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, good callout, updated!
0aba570
to
9590564
Compare
No New Or Fixed Issues Found |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
🎟️ Tracking
BIT-1212
🚧 Type of change
📔 Objective
Adds support for nested folders.
📋 Code changes
📸 Screenshots
Simulator.Screen.Recording.-.iPhone.15.Pro.-.2024-03-14.at.16.45.37.mp4
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes