Redesign #243
Redesign #243
Conversation
WalkthroughThe changes involve significant updates to various components and modules, focusing on sorting packages by publication time, enhancing keyword validation, and improving the display of package information. New components were introduced, existing components were modified for better functionality, and the data structures for packages were updated to enhance clarity and maintainability. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant Home
participant TopPackages
participant MainActor
User->>Home: View Home Page
Home->>TopPackages: Load Packages
TopPackages->>MainActor: getNewPackages()
MainActor-->>TopPackages: Return New Packages
TopPackages-->>Home: Display New Packages
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Validate keywords
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 6
Outside diff range, codebase verification and nitpick comments (2)
frontend/components/TopPackages.svelte (1)
Line range hint
8-21: Add Error Handling in onMount FunctionThe asynchronous function fetches data based on the
typebut lacks error handling. Consider adding a try-catch block to handle potential errors from themainActor()calls.Suggested modification:
onMount(async () => { + try { if (type === 'recently-updated') { packages = await mainActor().getRecentlyUpdatedPackages(); } else if (type === 'most-downloaded') { packages = await mainActor().getMostDownloadedPackagesIn7Days(); } else if (type === 'new') { packages = await mainActor().getNewPackages(); } loaded = true; + } catch (error) { + console.error('Failed to fetch packages:', error); + // Handle error state appropriately + } });frontend/components/PackagesByCategory.svelte (1)
23-25: Add tests forgetQualityPointsfunction.The
getQualityPointsfunction is crucial for sorting packages by quality. However, no tests were found for this function. Please ensure that comprehensive tests are added to cover various scenarios and edge cases to verify its correctness.
- File:
frontend/logic/get-quality-points.tsAnalysis chain
Ensure correct implementation of sorting logic.
The sorting logic uses the
getQualityPointsfunction to sort packages based on quality points. This is a significant enhancement as it prioritizes packages with higher quality scores. However, ensure that thegetQualityPointsfunction is thoroughly tested to handle all expected input cases effectively.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the implementation and test coverage for `getQualityPoints`. # Test: Search for the function implementation and associated tests. rg --type ts -A 5 $'getQualityPoints'Length of output: 433
Script:
#!/bin/bash # Search for the complete implementation of the `getQualityPoints` function. rg --type ts 'getQualityPoints' -A 20 # Search for test files that might contain tests for `getQualityPoints`. rg --type ts 'getQualityPoints' --glob '*test*'Length of output: 1456
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (14)
- backend/main/main-canister.mo (3 hunks)
- backend/main/registry/packagesByCategory.mo (8 hunks)
- backend/main/utils/validateConfig.mo (1 hunks)
- blog/blog/0-unlisted.md (1 hunks)
- frontend/components/Home.svelte (3 hunks)
- frontend/components/PackagesByCategory.svelte (6 hunks)
- frontend/components/RecentlyUpdatedPackages.svelte (1 hunks)
- frontend/components/TopPackages.svelte (2 hunks)
- frontend/components/package/Keywords.svelte (1 hunks)
- frontend/components/package/Package.svelte (5 hunks)
- frontend/components/package/PackageCard.svelte (4 hunks)
- frontend/components/package/PackageQualityIcon.svelte (2 hunks)
- frontend/components/package/PackageVersionSummary.svelte (3 hunks)
- frontend/logic/get-quality-points.ts (1 hunks)
Additional comments not posted (41)
frontend/components/package/Keywords.svelte (2)
1-5: Script block is correctly implemented.The TypeScript usage and the import statement are correctly implemented.
13-21: CSS is well-implemented.The use of flexbox and styling properties are appropriate for the keywords display. Good use of font properties for readability.
blog/blog/0-unlisted.md (1)
9-17: Markdown content is clear and well-structured.The descriptions of the new functionalities are clear and informative. The markdown syntax is used correctly.
frontend/components/RecentlyUpdatedPackages.svelte (2)
1-9: Imports and Initial Declarations: ApprovedThe imports and initial declarations are correctly set up for a Svelte component using TypeScript. The use of
PackageSummaryWithChangestype ensures type safety for thepackagesarray.
33-49: CSS Styling: ApprovedThe CSS styling uses flexbox, which is suitable for the component's layout requirements, ensuring a responsive design.
frontend/components/package/PackageQualityIcon.svelte (2)
1-3: Imports and Use of getQualityPoints: ApprovedThe import of
getQualityPointsfrom/logic/get-quality-pointscentralizes the logic for calculating quality points, enhancing maintainability and reducing complexity in this component.
1-1: SVG and Styling: ApprovedThe SVG implementation and associated styling are correctly set up to visually represent the quality points effectively.
Also applies to: 1-1
frontend/components/TopPackages.svelte (2)
Line range hint
1-8: Imports and Expansion of Type Variable: ApprovedThe expansion of the
typevariable to include 'new' is a positive change, enhancing the component's functionality by allowing it to handle more types of package displays. The imports are correctly set up for a Svelte component using TypeScript.
38-45: Simplify Conditional Rendering LogicThe nested conditional check for
loadedinside theelseblock of theeachloop is redundant since it's already within a parent conditional that checks ifloadedis true.Suggested modification:
{#if loaded} {#each packages as pkg} <PackageCard {pkg} showUpdated={type === 'recently-updated'} showFirstPublished={type === 'new'} showVersion={type === 'recently-updated'} show7DayDownloads={type === 'most-downloaded'} ></PackageCard> {:else} - {#if loaded} <div class="not-found">Packages not found</div> - {/if} {/each} {:else} <Loader></Loader> {/if}Likely invalid or redundant comment.
frontend/components/package/PackageCard.svelte (4)
10-10: Approved addition ofshowFirstPublishedproperty.This new property enhances the component's flexibility by allowing conditional display of the publication date.
34-36: Approved conditional rendering forshowFirstPublished.The implementation correctly checks the
showFirstPublishedproperty and uses theDatecomponent to display the publication date, maintaining consistency and enhancing user interface flexibility.
57-57: Approved style change for border color.The update from
var(--color-primary)tovar(--color-secondary)is a minor stylistic change that aligns with the overall design updates.
97-97: Approved addition ofline-clampproperty.The
line-clampproperty enhances the visual presentation by limiting the description display to two lines, which helps maintain a clean and concise layout.frontend/components/Home.svelte (3)
10-10: Approved addition ofRecentlyUpdatedPackagesimport.The new import statement enables the use of the
RecentlyUpdatedPackagescomponent, expanding the functionality of the home page.
48-48: Approved change inTopPackagescomponent usage.The adjustment to display packages categorized as "new" instead of "most-downloaded" aligns with a possible strategic shift or user feedback, enhancing the relevance of the displayed content.
145-147: Approved addition of.section.blockCSS class.The new CSS class ensures that the section containing the
RecentlyUpdatedPackagescomponent is displayed as a block element, maintaining visual consistency and enhancing the layout.frontend/components/package/PackageVersionSummary.svelte (5)
10-10: Approved addition ofshowNameproperty.The new
showNameproperty enhances the component's flexibility by allowing dynamic control over the visibility of the package name.
12-12: Approved dynamic URL construction usingshowName.The implementation smartly adapts the URL based on the visibility of the package name, enhancing the user experience by providing contextually appropriate links.
19-22: Approved HTML structure update.The updated HTML structure consolidates the package name and version into a single anchor tag, enhancing the presentation and improving usability.
90-104: Approved CSS class adjustments forshowName.The adjustments to the CSS classes ensure that the name and version are conditionally displayed based on the
showNameproperty, maintaining visual consistency and enhancing the component's adaptability.
116-118: Approved CSS class adjustment for word-breaking in dependency list.The adjustment to apply
word-break: break-wordensures that long dependency names do not overflow their container, maintaining a clean and readable layout.backend/main/registry/packagesByCategory.mo (9)
Line range hint
4-25: Approved: Data Structures category structure.The new object format for the "Data Structures" category is well-structured and enhances clarity.
Line range hint
26-44: Approved: Utilities category structure.The new object format for the "Utilities" category is well-structured and enhances clarity.
Line range hint
45-57: Approved: Encoding category structure.The new object format for the "Encoding" category is well-structured and enhances clarity.
Line range hint
58-70: Approved: Cryptography category structure.The new object format for the "Cryptography" category is well-structured and enhances clarity.
Line range hint
71-92: Approved: Types/Interfaces category structure.The new object format for the "Types/Interfaces" category is well-structured and enhances clarity.
Line range hint
93-110: Approved: HTTP category structure.The new object format for the "HTTP" category is well-structured and enhances clarity.
111-119: Approved: Async Data Flow category structure.The new object format for the "Async Data Flow" category is well-structured and enhances clarity.
120-128: Approved: Databases category structure.The new object format for the "Databases" category is well-structured and enhances clarity.
129-139: Approved: Stable Memory category structure.The new object format for the "Stable Memory" category is well-structured and enhances clarity.
frontend/components/package/Package.svelte (3)
25-25: Import statement forKeywordscomponent is correct.The import statement is correctly added and follows the existing pattern for component imports.
158-158: Addition of package description display is well-implemented.The new
<div>element for displaying the package description is correctly added and enhances the user interface.
168-168: Use of<Keywords>component for keyword handling is effective.The replacement of inline keyword rendering with the
<Keywords>component streamlines the code and promotes modularity.backend/main/main-canister.mo (2)
418-418: Renaming to_sortByPublicationTimealigns with updated sorting criteria.The function renaming is appropriate and reflects the new focus on sorting packages by publication time.
Line range hint
428-461: Updated sorting logic ingetPackagesByCategoryandgetNewPackagesfunctions is clear and effective.The modifications in these functions enhance the clarity and functionality by aligning the sorting operations with the focus on publication time.
frontend/components/PackagesByCategory.svelte (5)
7-8: Review of new imports and their usage.The imports for
getQualityPointsandKeywordsare correctly placed and used within the component. ThegetQualityPointsfunction is used to sort packages by quality points, which aligns with the PR objectives to enhance sorting by publication time and quality.The import statements and their usage are correctly implemented.
31-65: Review ofgetCategoryDescriptionfunction.The function
getCategoryDescriptionprovides detailed descriptions for each category, which enhances the user experience by offering more insights into the packages. This implementation is straightforward and aligns with the PR objectives to improve the display of package information.The implementation of
getCategoryDescriptionis correct and enhances the component's functionality.
67-101: Review ofgetCategoryKeywordsfunction.The function
getCategoryKeywordseffectively provides relevant keywords for each category. This addition is crucial for enhancing keyword validation and aligns with the PR objectives. The implementation is clean and straightforward.The implementation of
getCategoryKeywordsis correct and enhances the component's functionality.
115-115: Review of template updates for displaying category information.The template now includes a new section that displays the category description and associated keywords. This change is crucial for providing users with more context about the packages and enhances the overall user experience.
The template updates are correctly implemented and improve the component's usability.
Line range hint
162-191: Review of CSS updates.The CSS changes are aimed at improving the visual presentation of categories and descriptions. The styles are well-organized and enhance the layout without affecting the existing design principles.
The CSS updates are correctly implemented and improve the visual presentation of the component.
backend/main/utils/validateConfig.mo (1)
186-205: Enhanced keyword validation logic.The updated validation logic for keywords includes checks for minimum length, character restrictions, and disallowing consecutive hyphens. These enhancements significantly improve the robustness of keyword validation and align with the PR objectives to enhance keyword validation.
The enhancements to the keyword validation logic are correctly implemented and improve the integrity of the configuration.
| <div class="keywords"> | ||
| {#each keywords as keyword} | ||
| <a class="keyword" href="/search/keyword:{keyword}" use:link>#{keyword}</a> | ||
| {/each} | ||
| </div> |
There was a problem hiding this comment.
Correct the interpolation syntax in the anchor tag.
Svelte uses {} for interpolation, not #{}. Correct this to ensure the keywords are displayed properly.
Apply this diff to correct the interpolation syntax:
- <a class="keyword" href="/search/keyword:{keyword}" use:link>#{keyword}</a>
+ <a class="keyword" href="/search/keyword:{keyword}" use:link>{keyword}</a>Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| <div class="keywords"> | |
| {#each keywords as keyword} | |
| <a class="keyword" href="/search/keyword:{keyword}" use:link>#{keyword}</a> | |
| {/each} | |
| </div> | |
| <div class="keywords"> | |
| {#each keywords as keyword} | |
| <a class="keyword" href="/search/keyword:{keyword}" use:link>{keyword}</a> | |
| {/each} | |
| </div> |
| export let getQualityPoints = (quality : PackageQuality) => { | ||
| let maxBasePoints = 6; | ||
|
|
||
| let basePoints = | ||
| Number(quality.hasDescription) | ||
| + Number(quality.hasDocumentation) | ||
| + Number(quality.hasKeywords) | ||
| + Number(quality.hasLicense) | ||
| + Number(quality.hasRepository) | ||
| + Number(!('tooOld' in quality.depsStatus)); | ||
| let extraPoints = Number(quality.hasTests) + Number(quality.hasReleaseNotes) + Number('allLatest' in quality.depsStatus); | ||
|
|
||
| if (basePoints !== maxBasePoints) { | ||
| extraPoints = 0; | ||
| } | ||
|
|
||
| return { | ||
| base: basePoints, | ||
| extra: extraPoints, | ||
| total: basePoints + extraPoints, | ||
| }; |
There was a problem hiding this comment.
Refactor to use typical TypeScript conventions.
Consider using boolean values directly in arithmetic operations, which TypeScript handles gracefully, instead of converting them to numbers.
Apply this diff to refactor the code for typical TypeScript usage:
- let basePoints =
- Number(quality.hasDescription)
- + Number(quality.hasDocumentation)
- + Number(quality.hasKeywords)
- + Number(quality.hasLicense)
- + Number(quality.hasRepository)
- + Number(!('tooOld' in quality.depsStatus));
- let extraPoints = Number(quality.hasTests) + Number(quality.hasReleaseNotes) + Number('allLatest' in quality.depsStatus);
+ let basePoints =
+ (quality.hasDescription ? 1 : 0)
+ + (quality.hasDocumentation ? 1 : 0)
+ + (quality.hasKeywords ? 1 : 0)
+ + (quality.hasLicense ? 1 : 0)
+ + (quality.hasRepository ? 1 : 0)
+ + (!('tooOld' in quality.depsStatus) ? 1 : 0);
+ let extraPoints = (quality.hasTests ? 1 : 0) + (quality.hasReleaseNotes ? 1 : 0) + ('allLatest' in quality.depsStatus ? 1 : 0);Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| export let getQualityPoints = (quality : PackageQuality) => { | |
| let maxBasePoints = 6; | |
| let basePoints = | |
| Number(quality.hasDescription) | |
| + Number(quality.hasDocumentation) | |
| + Number(quality.hasKeywords) | |
| + Number(quality.hasLicense) | |
| + Number(quality.hasRepository) | |
| + Number(!('tooOld' in quality.depsStatus)); | |
| let extraPoints = Number(quality.hasTests) + Number(quality.hasReleaseNotes) + Number('allLatest' in quality.depsStatus); | |
| if (basePoints !== maxBasePoints) { | |
| extraPoints = 0; | |
| } | |
| return { | |
| base: basePoints, | |
| extra: extraPoints, | |
| total: basePoints + extraPoints, | |
| }; | |
| export let getQualityPoints = (quality : PackageQuality) => { | |
| let maxBasePoints = 6; | |
| let basePoints = | |
| (quality.hasDescription ? 1 : 0) | |
| + (quality.hasDocumentation ? 1 : 0) | |
| + (quality.hasKeywords ? 1 : 0) | |
| + (quality.hasLicense ? 1 : 0) | |
| + (quality.hasRepository ? 1 : 0) | |
| + (!('tooOld' in quality.depsStatus) ? 1 : 0); | |
| let extraPoints = (quality.hasTests ? 1 : 0) + (quality.hasReleaseNotes ? 1 : 0) + ('allLatest' in quality.depsStatus ? 1 : 0); | |
| if (basePoints !== maxBasePoints) { | |
| extraPoints = 0; | |
| } | |
| return { | |
| base: basePoints, | |
| extra: extraPoints, | |
| total: basePoints + extraPoints, | |
| }; |
| onMount(async () => { | ||
| packages = await mainActor().getRecentlyUpdatedPackages(); | ||
| loaded = true; | ||
| }); |
There was a problem hiding this comment.
Add Error Handling in onMount Function
The asynchronous function fetches data correctly but lacks error handling. Consider adding a try-catch block to handle potential errors from the mainActor().getRecentlyUpdatedPackages() call.
Suggested modification:
onMount(async () => {
+ try {
packages = await mainActor().getRecentlyUpdatedPackages();
loaded = true;
+ } catch (error) {
+ console.error('Failed to fetch packages:', error);
+ // Handle error state appropriately
+ }
});Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| onMount(async () => { | |
| packages = await mainActor().getRecentlyUpdatedPackages(); | |
| loaded = true; | |
| }); | |
| onMount(async () => { | |
| try { | |
| packages = await mainActor().getRecentlyUpdatedPackages(); | |
| loaded = true; | |
| } catch (error) { | |
| console.error('Failed to fetch packages:', error); | |
| // Handle error state appropriately | |
| } | |
| }); |
| {#if loaded} | ||
| {#each packages as pkg} | ||
| <PackageVersionSummary summary={pkg} showName={true}></PackageVersionSummary> | ||
| {:else} | ||
| {#if loaded} | ||
| <div class="not-found">Packages not found</div> | ||
| {/if} | ||
| {/each} | ||
| {:else} | ||
| <Loader></Loader> | ||
| {/if} |
There was a problem hiding this comment.
Simplify Conditional Rendering Logic
The nested conditional check for loaded inside the else block of the each loop is redundant since it's already within a parent conditional that checks if loaded is true.
Suggested modification:
{#if loaded}
{#each packages as pkg}
<PackageVersionSummary summary={pkg} showName={true}></PackageVersionSummary>
{:else}
- {#if loaded}
<div class="not-found">Packages not found</div>
- {/if}
{/each}
{:else}
<Loader></Loader>
{/if}Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| {#if loaded} | |
| {#each packages as pkg} | |
| <PackageVersionSummary summary={pkg} showName={true}></PackageVersionSummary> | |
| {:else} | |
| {#if loaded} | |
| <div class="not-found">Packages not found</div> | |
| {/if} | |
| {/each} | |
| {:else} | |
| <Loader></Loader> | |
| {/if} | |
| {#if loaded} | |
| {#each packages as pkg} | |
| <PackageVersionSummary summary={pkg} showName={true}></PackageVersionSummary> | |
| {:else} | |
| <div class="not-found">Packages not found</div> | |
| {/each} | |
| {:else} | |
| <Loader></Loader> | |
| {/if} |
| let points = getQualityPoints(pkg.quality); | ||
|
|
||
| function convertRange(value : number, r1 : [number, number], r2 : [number, number]) { | ||
| return (value - r1[0]) * (r2[1] - r2[0]) / (r1[1] - r1[0]) + r2[0]; | ||
| } | ||
|
|
||
| outerCircleDashOffset = convertRange(maxBasePoints - basePoints, [0, maxBasePoints], [18, 100]); | ||
| innerLineY = convertRange(maxExtraPoints - extraPoints, [0, maxExtraPoints], [13, 30]); | ||
| outerCircleDashOffset = convertRange(maxBasePoints - points.base, [0, maxBasePoints], [18, 100]); | ||
| innerLineY = convertRange(maxExtraPoints - points.extra, [0, maxExtraPoints], [13, 30]); |
There was a problem hiding this comment.
Enhance convertRange Function with Input Validation
The convertRange function is used to map values for visual representation but lacks input validation. Consider adding checks to ensure that the input values are within expected ranges to prevent runtime errors.
Suggested addition:
function convertRange(value : number, r1 : [number, number], r2 : [number, number]) {
+ if (r1[0] >= r1[1] || r2[0] >= r2[1]) {
+ throw new Error('Invalid range parameters');
+ }
return (value - r1[0]) * (r2[1] - r2[0]) / (r1[1] - r1[0]) + r2[0];
}Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| let points = getQualityPoints(pkg.quality); | |
| function convertRange(value : number, r1 : [number, number], r2 : [number, number]) { | |
| return (value - r1[0]) * (r2[1] - r2[0]) / (r1[1] - r1[0]) + r2[0]; | |
| } | |
| outerCircleDashOffset = convertRange(maxBasePoints - basePoints, [0, maxBasePoints], [18, 100]); | |
| innerLineY = convertRange(maxExtraPoints - extraPoints, [0, maxExtraPoints], [13, 30]); | |
| outerCircleDashOffset = convertRange(maxBasePoints - points.base, [0, maxBasePoints], [18, 100]); | |
| innerLineY = convertRange(maxExtraPoints - points.extra, [0, maxExtraPoints], [13, 30]); | |
| let points = getQualityPoints(pkg.quality); | |
| function convertRange(value : number, r1 : [number, number], r2 : [number, number]) { | |
| if (r1[0] >= r1[1] || r2[0] >= r2[1]) { | |
| throw new Error('Invalid range parameters'); | |
| } | |
| return (value - r1[0]) * (r2[1] - r2[0]) / (r1[1] - r1[0]) + r2[0]; | |
| } | |
| outerCircleDashOffset = convertRange(maxBasePoints - points.base, [0, maxBasePoints], [18, 100]); | |
| innerLineY = convertRange(maxExtraPoints - points.extra, [0, maxExtraPoints], [13, 30]); |
| let title = ''; | ||
| $: if (type === 'recently-updated') { | ||
| title = 'Recently Updated'; | ||
| } | ||
| else if (type === 'most-downloaded') { | ||
| title = 'Most Downloaded in 7 days'; | ||
| } | ||
| else if (type === 'new') { | ||
| title = 'New Packages'; | ||
| } |
There was a problem hiding this comment.
Simplify Title Setting Logic
The reactive statement correctly updates the title based on the type. Consider using a map or object to simplify the logic and reduce redundancy.
Suggested modification:
let title = '';
let titles = {
'recently-updated': 'Recently Updated',
'most-downloaded': 'Most Downloaded in 7 days',
'new': 'New Packages'
};
$: title = titles[type];Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| let title = ''; | |
| $: if (type === 'recently-updated') { | |
| title = 'Recently Updated'; | |
| } | |
| else if (type === 'most-downloaded') { | |
| title = 'Most Downloaded in 7 days'; | |
| } | |
| else if (type === 'new') { | |
| title = 'New Packages'; | |
| } | |
| let title = ''; | |
| let titles = { | |
| 'recently-updated': 'Recently Updated', | |
| 'most-downloaded': 'Most Downloaded in 7 days', | |
| 'new': 'New Packages' | |
| }; | |
| $: title = titles[type]; |
Summary by CodeRabbit
New Features
Improvements
Bug Fixes