chore: extract reactivity #42
Conversation
|
WalkthroughA new Changes
Sequence Diagram(s)sequenceDiagram
participant Consumer
participant unuse
participant unuse-reactivity
Consumer->>unuse: import { unSignal, unEffect, ... }
unuse->>unuse-reactivity: re-export primitives
unuse-reactivity-->>unuse: provides reactivity primitives
unuse-->>Consumer: exposes reactivity primitives
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
✨ Finishing Touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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 (
|
6c4d78c to
9e776ab
Compare
|
@JounQin please have a look into this and tell me if we are going a wrong way here or if this is fine with you. After this PR would get merged, my next step would be to create |
9e776ab to
cfde585
Compare
There was a problem hiding this comment.
Important
Looks good to me! 👍
Reviewed everything up to cfde585 in 1 minute and 49 seconds. Click for details.
- Reviewed
435lines of code in32files - Skipped
1files when reviewing. - Skipped posting
17draft comments. View those below. - Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.
1. packages/unuse-reactivity/tsdown.config.ts:6
- Draft comment:
Confirm that 'publint' is intentional; consider adding a comment explaining its purpose as it's less common. - Reason this comment was not posted:
Confidence changes required:33%<= threshold50%None
2. packages/unuse/package.json:31
- Draft comment:
Dependency on 'unuse-reactivity' using workspace:* looks correct; ensure that this version resolution fits your release strategy. - Reason this comment was not posted:
Confidence changes required:33%<= threshold50%None
3. packages/unuse/src/index.ts:1
- Draft comment:
Re-exporting all reactivity APIs from 'unuse-reactivity' centralizes the interface. Verify that consumers receive the correct updated types. - Reason this comment was not posted:
Confidence changes required:0%<= threshold50%None
4. packages/unuse/src/toUnSignal/index.ts:29
- Draft comment:
Consider consolidating the undefined and null checks (lines 30–36). For example, using a check like 'value == null' could simplify the code. - Reason this comment was not posted:
Confidence changes required:33%<= threshold50%None
5. packages/unuse/src/toUnSignal/index.ts:88
- Draft comment:
In the React branch, the hack that mutates the state array (lines ~88–103) can break React hook invariants. Document the risks and consider a safer synchronization method. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
6. packages/unuse/src/unResolve/index.ts:111
- Draft comment:
In the Angular branch, overriding the Angular signal's 'set' and 'update' methods is risky. While marked with a HACK, consider adding additional error handling or comments clarifying the potential side effects. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
7. packages/unuse/src/unResolve/index.ts:135
- Draft comment:
In the React branch, directly mutating the result of useState (lines ~138–157) is a dangerous hack that may break React's state consistency. Ensure this workaround is well tested and documented. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
8. packages/unuse/src/unResolve/index.ts:177
- Draft comment:
The Solid branch similarly overrides the setter (lines ~180–208). This hack may lead to unpredictable behavior; consider reinforcing its safety with additional checks. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
9. packages/unuse/src/unResolve/index.ts:130
- Draft comment:
There are multiple '@ts-expect-error' comments (e.g. near lines 132 and 207). Consider revisiting these to improve type safety and reduce reliance on error suppression. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
10. packages/unuse/src/useEventListener/index.ts:170
- Draft comment:
The computed dependency (computedForWatch) aggregates targets, events, and listeners. Review these dependencies to ensure they do not trigger excessive re-renders or unintended re-registering of listeners. - Reason this comment was not posted:
Confidence changes required:33%<= threshold50%None
11. packages/unuse/src/useIntervalFn/index.ts:95
- Draft comment:
The condition checking if 'interval' is reactive (isUnRef(interval) || typeof interval === 'function') should be carefully reviewed to ensure it covers all edge cases. - Reason this comment was not posted:
Confidence changes required:33%<= threshold50%None
12. packages/unuse/src/useWebSocket/index.ts:288
- Draft comment:
In the auto-reconnect logic, ensure the 'checkRetires' function correctly handles both numeric and functional 'retries'. Edge cases should be considered to avoid infinite retries or premature stop. - Reason this comment was not posted:
Comment was not on a location in the diff, so it can't be submitted as a review comment.
13. packages/unuse/src/useWebSocket/index.ts:310
- Draft comment:
The ws.onerror handler currently just calls the optional onError callback. Consider logging errors or adding more context to aid in debugging socket issues. - Reason this comment was not posted:
Confidence changes required:33%<= threshold50%None
14. packages/unuse-reactivity/README.md:7
- Draft comment:
Typographical suggestion: Consider changing "We just working on it." to "We are just working on it." or "We're just working on it." for improved clarity. - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% While the grammar correction is technically correct, our rules state we should focus on code logic issues, not minor text improvements. Documentation typos and grammar, unless severely impacting understanding, are not worth commenting on. This is a very minor grammatical issue that doesn't impact comprehension. The grammar error could make the project look unprofessional. Poor documentation quality might reflect badly on the project. While professionalism matters, this is a minor grammatical issue in a README that's explicitly marked as "UNDER CONSTRUCTION". The meaning is still clear despite the grammar mistake. Delete the comment as it's too minor and focuses on documentation style rather than code logic or functionality.
15. packages/unuse-reactivity/tsdown.config.ts:6
- Draft comment:
There's a potential typo in the property name on line 6: 'publint' may be a typo for 'public' or another intended word. Could you please check this? - Reason this comment was not posted:
Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50% Since this is a configuration file for 'tsdown', 'publint' is very likely an intentional configuration option name, not a typo. Configuration options in build tools often have specific names that might look unusual. Without strong evidence that this is actually a typo, we should not keep a comment that speculates about it. I could be wrong if 'publint' is not actually a valid configuration option for tsdown. I haven't verified the tsdown documentation. Even if I haven't verified the docs, the comment is speculative ("may be a typo") and asks for confirmation, which violates our rules about not asking authors to verify things. Delete the comment as it's speculative and asks for verification, which violates our review rules.
16. packages/unuse/src/unResolve/index.solid.spec.ts:8
- Draft comment:
Typographical note: The test description reads "should resolve to an Solid Signal". Consider changing "an Solid" to "a Solid" since 'Solid' begins with a consonant sound. - Reason this comment was not posted:
Comment was on unchanged code.
17. packages/unuse/src/unResolve/index.vue.spec.ts:8
- Draft comment:
Typographical error: In the test description, it reads "should resolve to an Vue Ref". Consider changing "an Vue Ref" to "a Vue Ref". - Reason this comment was not posted:
Comment was on unchanged code.
Workflow ID: wflow_VNSaFluJrBLiUQGa
You can customize 
There was a problem hiding this comment.
Actionable comments posted: 0
♻️ Duplicate comments (11)
packages/unuse/src/toUnSignal/index.spec.ts (1)
1-1: Same module-resolution concern as noted inunAccess/index.spec.ts; please apply the chosen fix consistently.packages/unuse/src/toUnSignal/index.vue.spec.ts (1)
1-1: Same module-resolution concern as noted inunAccess/index.spec.ts; please apply the chosen fix consistently.packages/unuse/src/unResolve/index.solid.spec.ts (1)
2-2: Same module-resolution concern as noted inunAccess/index.spec.ts; please apply the chosen fix consistently.packages/unuse/src/toUnSignal/index.react.spec.ts (1)
5-5: Same resolution concern forunuse-reactivitySee the remark in
unResolve/index.react.spec.ts; the same applies here.packages/unuse/src/unResolve/index.vue.spec.ts (1)
1-1: Ensure Vue test can resolve the new packageSame module-resolution note as in the React spec – configure ESLint / TS paths so
unuse-reactivityis recognised.packages/unuse/src/unResolve/index.angular.spec.ts (1)
9-9: Angular test uses the new package – verify tooling pathsReplicating the earlier comment: add/verify workspace & TS path config so
unuse-reactivityresolves for ESLint and the Angular compiler.packages/unuse/src/toUnSignal/index.solid.spec.ts (1)
2-2: Solid test – same module-resolution caveatConfirm that
unuse-reactivityis resolvable for ESLint/Vitest in the Solid suite as well.packages/unuse/package.json (1)
30-31: Dual dependencies are justified per previous discussion.As noted in previous comments, both dependencies serve different purposes during this transition:
alien-signals: Prevents external bundling while still depending on itunuse-reactivity: Internal package to be inlined vianoExternalconfigurationpackages/unuse/src/useEventListener/index.ts (1)
3-3: Unresolved import warning – see earlier commentSame
'unuse-reactivity'resolution issue as flagged inunResolve.packages/unuse/src/toUnSignal/index.ts (1)
3-5: Unresolved import warning – see earlier commentSame
'unuse-reactivity'resolution issue.packages/unuse/src/unAccess/index.ts (1)
14-15: Unresolved import warning – see earlier commentSame
'unuse-reactivity'resolution issue.
🧹 Nitpick comments (6)
packages/unuse-reactivity/package.json (1)
5-7: Add missing build-time dependencies and clarify side-effects
tsdownis invoked in the build script yet isn’t listed indevDependencies, and the package doesn’t declare whether its modules are free of side-effects (important for tree-shaking). Consider:"scripts": { "build": "tsdown" }, + "sideEffects": false, + "devDependencies": { + "tsdown": "^x.y.z" // keep in sync with the root-level version + },Including these fields eliminates “command not found” errors in CI and helps bundlers optimise consumers’ bundles.
Also applies to: 30-35
packages/unuse/src/unResolve/index.react.spec.ts (1)
4-4: Make sure the new workspace package can be resolved in all tooling
unuse-reactivityis now referenced as an external module, but ESLint reports it as unresolved.
Double-check that:
packages/unuse-reactivity/package.jsoncontains"name": "unuse-reactivity"- The workspace root (or
eslint-import-resolver) is configured to pick up workspaces/PNPM packagestsconfig.base.json(or the config used by Vitest) has apathsentry if strict module resolution is enabledOtherwise IDE red squiggles and CI lint steps will keep failing even though the code runs.
packages/unuse/src/toUnSignal/index.react.spec.ts (1)
28-33: Remove profanity and clarify the TODOThe comment block contains informal/profane wording (“WHAT THE F***? IT'S BREAKING THE LAW”).
Please rephrase or remove – test code is part of the public surface and should stay professional.- // TODO @Shinigami92 2025-06-21: Check why this is not working - // WHAT THE FUCK? IT'S BREAKING THE LAW + // TODO(@Shinigami92): Investigate why this state-sync test failspackages/unuse/src/unResolve/index.ts (1)
110-112: Minor: mark value-only imports to improve tree-shaking
unComputedandunEffectare runtime values, butUnComputed/UnSignalare types.
You can help modern bundlers by splitting them:-import type { UnComputed, UnSignal } from 'unuse-reactivity'; -import { unComputed, unEffect } from 'unuse-reactivity'; +import type { UnComputed, UnSignal } from 'unuse-reactivity'; +import { unComputed, unEffect } from 'unuse-reactivity'; // keep(Looks identical but keeps type-only import separate; some bundlers still benefit.)
packages/unuse-reactivity/README.md (2)
7-7: Fix grammatical issues in the documentation.The tex 8000 t has grammatical errors that should be corrected for better documentation quality.
Apply this diff to fix the grammar:
-Right now there is no stable version of `unuse` available. We just working on it. +Right now, there is no stable version of `unuse` available. We are just working on it.
9-9: Add alt text to the image for accessibility.The image should include alt text to improve accessibility.
Apply this diff to add alt text:
-<img src="https://chronicle-brightspot.s3.amazonaws.com/6a/c4/00e4ab3143f7e0cf4d9fd33aa00b/constructocat2.jpg" width="400px" /> +<img src="https://chronicle-brightspot.s3.amazonaws.com/6a/c4/00e4ab3143f7e0cf4d9fd33aa00b/constructocat2.jpg" width="400px" alt="Construction cat illustration" />
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (24)
packages/unuse-reactivity/README.md(1 hunks)packages/unuse-reactivity/package.json(1 hunks)packages/unuse-reactivity/src/index.ts(1 hunks)packages/unuse-reactivity/tsdown.config.ts(1 hunks)packages/unuse/package.json(1 hunks)packages/unuse/src/index.ts(1 hunks)packages/unuse/src/toUnSignal/index.angular.spec.ts(1 hunks)packages/unuse/src/toUnSignal/index.react.spec.ts(1 hunks)packages/unuse/src/toUnSignal/index.solid.spec.ts(1 hunks)packages/unuse/src/toUnSignal/index.spec.ts(1 hunks)packages/unuse/src/toUnSignal/index.ts(1 hunks)packages/unuse/src/toUnSignal/index.vue.spec.ts(1 hunks)packages/unuse/src/unAccess/index.spec.ts(1 hunks)packages/unuse/src/unAccess/index.ts(1 hunks)packages/unuse/src/unResolve/index.angular.spec.ts(1 hunks)packages/unuse/src/unResolve/index.react.spec.ts(1 hunks)packages/unuse/src/unResolve/index.solid.spec.ts(1 hunks)packages/unuse/src/unResolve/index.spec.ts(1 hunks)packages/unuse/src/unResolve/index.ts(1 hunks)packages/unuse/src/unResolve/index.vue.spec.ts(1 hunks)packages/unuse/src/useEventListener/index.ts(1 hunks)packages/unuse/src/useIntervalFn/index.ts(1 hunks)packages/unuse/src/useWebSocket/index.ts(1 hunks)packages/unuse/tsdown.config.ts(1 hunks)
🧰 Additional context used
🪛 ESLint
packages/unuse/src/unAccess/index.spec.ts
[error] 1-1: Unable to resolve path to module 'unuse-reactivity'.
(import-x/no-unresolved)
packages/unuse/src/unResolve/index.vue.spec.ts
[error] 1-1: Unable to resolve path to module 'unuse-reactivity'.
(import-x/no-unresolved)
packages/unuse/src/unResolve/index.react.spec.ts
[error] 4-4: Unable to resolve path to module 'unuse-reactivity'.
(import-x/no-unresolved)
packages/unuse/src/unResolve/index.angular.spec.ts
[error] 9-9: Unable to resolve path to module 'unuse-reactivity'.
(import-x/no-unresolved)
packages/unuse/src/toUnSignal/index.vue.spec.ts
[error] 1-1: Unable to resolve path to module 'unuse-reactivity'.
(import-x/no-unresolved)
packages/unuse/src/unResolve/index.solid.spec.ts
[error] 2-2: Unable to resolve path to module 'unuse-reactivity'.
(import-x/no-unresolved)
packages/unuse/src/toUnSignal/index.react.spec.ts
[error] 5-5: Unable to resolve path to module 'unuse-reactivity'.
(import-x/no-unresolved)
packages/unuse/src/toUnSignal/index.spec.ts
[error] 1-1: Unable to resolve path to module 'unuse-reactivity'.
(import-x/no-unresolved)
packages/unuse/src/useWebSocket/index.ts
[error] 2-2: Unable to resolve path to module 'unuse-reactivity'.
(import-x/no-unresolved)
packages/unuse/src/toUnSignal/index.angular.spec.ts
[error] 10-10: Unable to resolve path to module 'unuse-reactivity'.
(import-x/no-unresolved)
packages/unuse/src/toUnSignal/index.solid.spec.ts
[error] 2-2: Unable to resolve path to module 'unuse-reactivity'.
(import-x/no-unresolved)
packages/unuse/src/unAccess/index.ts
[error] 15-15: Unable to resolve path to module 'unuse-reactivity'.
(import-x/no-unresolved)
packages/unuse/src/useIntervalFn/index.ts
[error] 1-1: Unable to resolve path to module 'unuse-reactivity'.
(import-x/no-unresolved)
packages/unuse-reactivity/tsdown.config.ts
[error] 1-1: Unable to resolve path to module 'tsdown'.
(import-x/no-unresolved)
packages/unuse/src/useEventListener/index.ts
[error] 3-3: Unable to resolve path to module 'unuse-reactivity'.
(import-x/no-unresolved)
packages/unuse/src/toUnSignal/index.ts
[error] 4-4: Unable to resolve path to module 'unuse-reactivity'.
(import-x/no-unresolved)
packages/unuse/src/unResolve/index.spec.ts
[error] 1-1: Unable to resolve path to module 'unuse-reactivity'.
(import-x/no-unresolved)
packages/unuse/src/unResolve/index.ts
[error] 11-11: Unable to resolve path to module 'unuse-reactivity'.
(import-x/no-unresolved)
packages/unuse/src/index.ts
[error] 1-1: Unable to resolve path to module 'unuse-reactivity'.
(import-x/no-unresolved)
🪛 LanguageTool
packages/unuse-reactivity/README.md
[typographical] ~6-~6: It appears that a comma is missing after this introductory phrase.
Context: ...ng noExternal. # UNDER CONSTRUCTION Right now there is no stable version of unuse a...
(RIGHT_NOW_PUNCTUATION_COMMA)
[grammar] ~7-~7: An auxiliary verb seems to be missing from this progressive structure. Did you mean “We're just working”, “We are just working”, or “We were just working”?
Context: ...no stable version of unuse available. We just working on it. <img src="https://chronicle-bri...
(PRP_VBG)
🪛 markdownlint-cli2 (0.17.2)
packages/unuse-reactivity/README.md
9-9: Images should have alternate text (alt text)
null
(MD045, no-alt-text)
🔇 Additional comments (11)
packages/unuse/src/unAccess/index.spec.ts (1)
1-1: Verify test-time resolution of the new package importVitest/TS-Node will try to load
unuse-reactivityvia./dist/index.jsas defined in the package’s exports.
If the package is not built before running tests, this line will throw “Cannot find module ‘unuse-reactivity’”.Options:
- Pre-build the workspace packages before
vitest:// root package.json { "scripts": { "test": "pnpm -r build && vitest" } }- Or let Vitest compile source by adding a path alias:
// tsconfig.base.json { "paths": { "unuse-reactivity": ["packages/unuse-reactivity/src/index.ts"] } }Please ensure one of these is in place; otherwise CI will start failing.
packages/unuse/src/toUnSignal/index.angular.spec.ts (1)
9-10: LGTM - Import refactoring aligns with reactivity extraction.The import statements have been correctly updated to use the new
unuse-reactivitypackage instead of local modules.However, please verify the workspace package setup to resolve the ESLint module resolution errors:
#!/bin/bash # Verify workspace package structure and dependencies echo "Checking workspace structure..." fd -t d "unuse-reactivity" packages/ echo -e "\nChecking package.json files..." fd "package.json" packages/ --exec cat {} \; --exec echo "---" echo -e "\nChecking if unuse-reactivity is built..." ls -la packages/unuse-reactivity/dist/ 2>/dev/null || echo "dist directory not found"packages/unuse/src/useWebSocket/index.ts (1)
2-2: Excellent import consolidation.The consolidation of
unSignalandunWatchimports from separate local modules into a single import fromunuse-reactivityimproves code organization and aligns with the reactivity extraction goals.packages/unuse/src/useIntervalFn/index.ts (1)
1-1: Clean import consolidation matches the refactoring pattern.The consolidation of
unSignalandunWatchimports aligns with the reactivity extraction across the codebase.packages/unuse/tsdown.config.ts (1)
7-7: Essential configuration for internal package bundling.The
noExternal: ['unuse-reactivity']configuration is crucial for the reactivity extraction architecture. It ensures thatunuse-reactivitycode is bundled directly into theunusedistribution rather than being treated as an external dependency, supporting the goal of keepingunuse-reactivityas an internal package.packages/unuse/src/unResolve/index.spec.ts (1)
1-1: ESLint flags the new'unuse-reactivity'path as unresolved – ensure Node/Vitest can actually resolve it
import { … } from 'unuse-reactivity';is now used across all test files, but the ESLint ruleimport-x/no-unresolvedcannot find that package.
Double-check that at least one of the following is true before CI runs the test suite:
packages/unuse-reactivity/package.jsonis built (orts-node-ready) and has the correct"exports"/"main"fields so that plainnoderesolution works.- Your monorepo tooling (pnpm-workspace, Yarn workspaces, etc.) installs the package into the root
node_modules.- Vitest/TS config contains a
paths/aliasentry such as// vitest.config.ts or tsconfig.json resolve: { alias: { 'unuse-reactivity': fileURLToPath(new URL('../../unuse-reactivity/src', import.meta.url)) } }Without one of those, runtime will fail even if the bundler setup passes.
packages/unuse/src/unResolve/index.ts (1)
10-12: Same unresolved-module issue applies to source code – set up path mapping or workspace dependencyAll runtime code now imports from
'unuse-reactivity'. Make sure the package appears in
packages/unuse/package.jsondependencies (not only in the root) and
tsconfig.build.json/rollup/tsupexternal/noExternalconfig is updated accordingly, otherwise:
tsc/ ESLint will continue to yell (import-x/no-unresolved);npm packof@un-ts/unusewill ship unresolved bare imports.If your intent is to bundle the inner package, add something like:
// tsdown.config.ts (inside unuse) noExternal: ['unuse-reactivity'], alias: { 'unuse-reactivity': '../unuse-reactivity/src' },Please verify with a cold install + build.
packages/unuse-reactivity/tsdown.config.ts (1)
1-7: LGTM! Standard tsdown configuration for a TypeScript package.The configuration appropriately sets up the build for a neutral platform library with export handling and public API linting enabled. The ESLint error about unresolved 'tsdown' is likely a false positive related to workspace dependency resolution.
packages/unuse-reactivity/src/index.ts (1)
1-5: LGTM! Clean barrel export pattern for the reactivity system.This consolidates the core reactivity modules (
unComputed,unEffect,unEffectScope,unSignal,unWatch) into a single entry point, providing a clean API surface for the extracted reactivity system. This aligns well with the PR objective to modularize the reactivity functionality.packages/unuse-reactivity/README.md (1)
3-3: Good explanation of the package purpose.The README clearly explains that
unuse-reactivityis an internal package compiled intounuse's distribution vianoExternal, which aligns with the PR objectives.packages/unuse/src/index.ts (1)
1-1: Excellent architectural change - clean extraction of reactivity system.This change successfully extracts the reactivity functionality into the separate
unuse-reactivitypackage while maintaining the same public API surface. The approach aligns perfectly with the PR objectives to modularize the reactivity system and prepare for future enhancements like addingunEffect.The ESLint error about unresolved 'unuse-reactivity' is expected during development and should resolve once the workspace dependencies are properly configured with the
noExternalbundling.
based on #28
extracts the reactivity signals into its own package, but does not publish it
instead it is marked as
noExternaland bundled intounuse's distthis is a preparation to enhance the reactivity system with more stuff like unEffect and dependency tracking as started and shown in #27 and #22 by @teleskop150750
Important
Extracts reactivity signals into
unuse-reactivitypackage, bundled intounuse, preparing for future enhancements.unuse-reactivitypackage, bundled intounuseusingnoExternal.unEffectand dependency tracking.unComputed,unEffect,unEffectScope,unSignal,unWatchfromunuse/srctounuse-reactivity/src.package.jsonandtsdown.config.tsforunuse-reactivity.unuse/package.jsonto includeunuse-reactivityas a dependency.unuse/srcto useunuse-reactivityfor reactivity functions.toUnSignalandunResolveto useunuse-reactivity.This description was created by
for cfde585. You can customize this summary. It will automatically update as commits are pushed.
Summary by CodeRabbit
New Features
Documentation
Chores
Refactor