Skip to content

Conversation

@leehuwuj
Copy link
Collaborator

@leehuwuj leehuwuj commented Apr 3, 2025

Summary by CodeRabbit

  • Refactor
    • Simplified storage configuration by using a constant for storage directory instead of a configuration class.
    • Enhanced workflow initialization with improved error handling for index validation before retrieving the query tool.
  • Chores
    • Added an update patch that further simplifies local index management.

…storage directory. This simplifies the code and improves readability.
@changeset-bot
Copy link

changeset-bot bot commented Apr 3, 2025

🦋 Changeset detected

Latest commit: ab1127c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
create-llama Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@leehuwuj leehuwuj requested a review from marcusschiesser April 3, 2025 03:49
@coderabbitai
Copy link

coderabbitai bot commented Apr 3, 2025

Walkthrough

This pull request removes the IndexConfig class from the index module and replaces its usage with a constant STORAGE_DIR set to "storage". The create_workflow function now validates the index before proceeding with query tool creation, raising a RuntimeError if the index is not found. Additionally, a new patch file is introduced to simplify local index code.

Changes

File(s) Change Summary
templates/.../index.py Removed IndexConfig class and its method from_default; updated get_index to read STORAGE_DIR directly.
templates/.../workflow.py Modified create_workflow to first retrieve and validate the index, raising a RuntimeError if the index is absent before proceeding.
.changeset/grumpy-tigers-heal.md Added a new patch file titled "create-llama" that simplifies the local index code.
templates/.../generate.py Removed retrieval of storage directory from environment variable; now uses STORAGE_DIR constant directly. Updated logging statements accordingly.

Suggested reviewers

  • marcusschiesser

Poem

I'm hopping through code with a joyful beat,
Dropping the old class, oh so neat.
Environment vars lead my rabbit trail,
Valid indexes never fail.
With each line I nibble and cheer,
A bunny celebrates change all year!
🥕🐇

✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

…ings. Updated imports and initialization to support UI configuration, including enabling/disabling the UI and setting starter questions. Adjusted tests to validate UI configuration functionality.
@leehuwuj leehuwuj changed the title chore: simplify local index code chore: simplify local index and add ui config Apr 3, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 015b398 and b61613b.

📒 Files selected for processing (3)
  • llama-index-server/llama_index/server/__init__.py (1 hunks)
  • llama-index-server/llama_index/server/server.py (5 hunks)
  • llama-index-server/tests/test_llamaindex_server.py (4 hunks)
🧰 Additional context used
🧬 Code Definitions (1)
llama-index-server/llama_index/server/__init__.py (1)
llama-index-server/llama_index/server/server.py (2)
  • LlamaIndexServer (39-197)
  • UIConfig (17-36)
🪛 GitHub Actions: Build Package
llama-index-server/tests/test_llamaindex_server.py

[error] 100-100: KeyError: 'TITLE' in test_ui_is_downloaded. The expected key 'TITLE' was not found in the config JSON.


[error] 190-190: KeyError: 'TITLE' in test_ui_config_from_dict. The expected key 'TITLE' was not found in the config JSON.

⏰ Context from checks skipped due to timeout of 90000ms (27)
  • GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --llamacloud)
  • GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --example-file)
  • GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --no-files)
  • GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --llamacloud)
  • GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --example-file)
  • GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --no-files)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --llamacloud)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --example-file)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --no-files)
  • GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --llamacloud)
  • GitHub Check: typescript (18, 3.11, ubuntu-22.04, nextjs, --llamacloud)
  • GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --example-file)
  • GitHub Check: typescript (18, 3.11, ubuntu-22.04, nextjs, --example-file)
  • GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --no-files)
  • GitHub Check: typescript (18, 3.11, ubuntu-22.04, nextjs, --no-files)
  • GitHub Check: typescript (18, 3.11, windows-latest, nextjs, --llamacloud)
  • GitHub Check: python (20, 3.11, windows-latest, fastapi, --llamacloud)
  • GitHub Check: typescript (18, 3.11, windows-latest, nextjs, --example-file)
  • GitHub Check: python (20, 3.11, windows-latest, fastapi, --example-file)
  • GitHub Check: typescript (18, 3.11, windows-latest, nextjs, --no-files)
  • GitHub Check: python (20, 3.11, windows-latest, fastapi, --no-files)
  • GitHub Check: typescript (18, 3.11, macos-latest, nextjs, --llamacloud)
  • GitHub Check: python (20, 3.11, macos-latest, fastapi, --llamacloud)
  • GitHub Check: typescript (18, 3.11, macos-latest, nextjs, --example-file)
  • GitHub Check: python (20, 3.11, macos-latest, fastapi, --example-file)
  • GitHub Check: typescript (18, 3.11, macos-latest, nextjs, --no-files)
  • GitHub Check: python (20, 3.11, macos-latest, fastapi, --no-files)
🔇 Additional comments (15)
llama-index-server/llama_index/server/__init__.py (2)

1-1: LGTM: Proper import statement with UIConfig.

The import statement now includes the new UIConfig class along with LlamaIndexServer, which is consistent with the objective of making the UI configuration more accessible.


3-3: LGTM: UIConfig correctly added to __all__.

Adding UIConfig to the __all__ list makes it part of the public API, allowing users to import it directly from llama_index.server. This is consistent with the simplified approach of managing UI configuration.

llama-index-server/tests/test_llamaindex_server.py (4)

1-4: LGTM: Added necessary imports for enhanced testing.

The additional imports (json, os, shutil) and the updated import for UIConfig are appropriate for the new test functionality.

Also applies to: 10-10


43-43: LGTM: Improved route checking method.

Changed the route check from direct path comparison to string-based search, which is more resilient to route representation changes.


69-80: LGTM: Updated server configuration to use UIConfig.

Properly configured the test to use the new UIConfig class, ensuring that UI features are properly tested with the new configuration approach.


130-153: LGTM: Good test for UI config customization.

This test verifies that custom UI configurations are properly applied, ensuring robust UI customization capabilities.

llama-index-server/llama_index/server/server.py (9)

4-4: LGTM: Updated imports to support new features.

Added necessary imports for Union and BaseModel to support the new UIConfig class.

Also applies to: 9-10


17-37: LGTM: Well-structured UIConfig class.

The new UIConfig class is well-designed with appropriate defaults and a clear method for generating configuration content. The encapsulation of UI configuration settings in a Pydantic model is a good practice.


42-42: LGTM: Added UI configuration attribute.

Added ui_config attribute with the proper type annotation.


50-50: LGTM: Updated method signature and documentation.

The constructor parameter and its documentation have been updated to use the new UIConfig class.

Also applies to: 65-65


76-81: LGTM: Robust initialization logic for UI configuration.

The initialization logic handles three cases gracefully:

  1. No configuration provided (creates default)
  2. Dictionary provided (converts to UIConfig)
  3. UIConfig instance provided (uses as-is)

This provides flexibility for users while maintaining type safety.


94-97: LGTM: Updated UI enabling logic.

Updated the conditional checks to use the new ui_config.enabled property, maintaining the same behavior in a more structured way.


99-99: LGTM: Updated mount UI condition.

Updated the condition to use the new ui_config.enabled property consistently.


125-133: LGTM: Updated mount UI implementation.

The updated implementation uses the new ui_config properties consistently throughout the method, removing redundancy.


141-147: LGTM: Updated UI config override method.

The method now uses the ui_config properties and get_config_content method for a more encapsulated approach.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
llama-index-server/llama_index/server/server.py (2)

94-97: Redundant UI enabling logic could be simplified.

The logic for setting the enabled attribute of ui_config is complex with multiple is None checks. Since the enabled attribute has a default value of True in the UIConfig class, it will never be None unless explicitly set.

Consider simplifying the logic:

- if str(env).lower() == "dev":
-     self.allow_cors("*")
-     if self.ui_config.enabled is None:
-         self.ui_config.enabled = True
- if self.ui_config.enabled is None:
-     self.ui_config.enabled = False
+ if str(env).lower() == "dev":
+     self.allow_cors("*")
+     # In dev environment, ensure UI is enabled unless explicitly disabled
+     if not isinstance(self.ui_config.enabled, bool):
+         self.ui_config.enabled = True
+ # In non-dev environments, UI is disabled by default unless explicitly enabled
+ elif not isinstance(self.ui_config.enabled, bool):
+     self.ui_config.enabled = False

125-125: Redundant UI enabled check.

This check is redundant since the method mount_ui is only called if self.ui_config.enabled is truthy (Line 99).

- if self.ui_config.enabled:
-     if not os.path.exists(self.ui_config.ui_path):
+ if not os.path.exists(self.ui_config.ui_path):
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b61613b and 389ef02.

📒 Files selected for processing (1)
  • llama-index-server/llama_index/server/server.py (5 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (28)
  • GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --llamacloud)
  • GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --example-file)
  • GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --no-files)
  • GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --llamacloud)
  • GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --example-file)
  • GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --no-files)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --llamacloud)
  • GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --llamacloud)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --example-file)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --no-files)
  • GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --example-file)
  • GitHub Check: typescript (18, 3.11, ubuntu-22.04, nextjs, --llamacloud)
  • GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --no-files)
  • GitHub Check: typescript (18, 3.11, ubuntu-22.04, nextjs, --example-file)
  • GitHub Check: typescript (18, 3.11, ubuntu-22.04, nextjs, --no-files)
  • GitHub Check: typescript (18, 3.11, windows-latest, nextjs, --llamacloud)
  • GitHub Check: python (20, 3.11, windows-latest, fastapi, --llamacloud)
  • GitHub Check: typescript (18, 3.11, windows-latest, nextjs, --example-file)
  • GitHub Check: typescript (18, 3.11, windows-latest, nextjs, --no-files)
  • GitHub Check: python (20, 3.11, windows-latest, fastapi, --example-file)
  • GitHub Check: typescript (18, 3.11, macos-latest, nextjs, --llamacloud)
  • GitHub Check: python (20, 3.11, windows-latest, fastapi, --no-files)
  • GitHub Check: python (20, 3.11, macos-latest, fastapi, --llamacloud)
  • GitHub Check: typescript (18, 3.11, macos-latest, nextjs, --example-file)
  • GitHub Check: python (20, 3.11, macos-latest, fastapi, --example-file)
  • GitHub Check: Unit Tests (windows-latest, 3.9)
  • GitHub Check: typescript (18, 3.11, macos-latest, nextjs, --no-files)
  • GitHub Check: python (20, 3.11, macos-latest, fastapi, --no-files)
🔇 Additional comments (4)
llama-index-server/llama_index/server/server.py (4)

17-37: Well-structured UI configuration class!

The UIConfig class nicely encapsulates UI-related settings using Pydantic, which provides automatic validation and type checking. The default values make the configuration easy to use out of the box.


42-42: Good refactoring of UI configuration into a single attribute.

This is in line with the suggestion from the previous review comment to use a single parameter for UI configuration.


50-50: Nice implementation of flexible UI configuration initialization.

The ability to accept either a UIConfig instance or a dictionary provides flexibility for users while maintaining type safety. The initialization logic properly handles all cases.

Also applies to: 76-81


146-146: Clean UI config content generation!

The code uses the get_config_content method of the UIConfig class, which is a good approach for encapsulating this functionality.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
llama-index-server/README.md (2)

46-50: UI Configuration in Quick Start Example:
The example instantiation of LlamaIndexServer now uses a ui_config dictionary—which is great for consolidating UI settings. The provided keys (app_title and starter_questions) are clear. Consider adding a brief comment or annotation noting that additional options (e.g., enabled and ui_path) exist for further customization.


69-69: Outdated Parameter Reference in Documentation:
In the Quick Start instructions, the text still refers to setting include_ui=True. Since this parameter was replaced by ui_config (with its enabled option), please update this reference to avoid confusion. For example, you might suggest:

- Access the chat UI at `http://localhost:8000/` (Make sure you set the `env="dev"` or `include_ui=True` in the server configuration)
+ Access the chat UI at `http://localhost:8000/` (Make sure you set the `env="dev"` or configure `ui_config` with `enabled: True` in the server configuration)
📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 791e2a7 and d9ffd01.

📒 Files selected for processing (1)
  • llama-index-server/README.md (2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (23)
  • GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --llamacloud)
  • GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --example-file)
  • GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --no-files)
  • GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --llamacloud)
  • GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --example-file)
  • GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --no-files)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --llamacloud)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --example-file)
  • GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --llamacloud)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --no-files)
  • GitHub Check: typescript (18, 3.11, ubuntu-22.04, nextjs, --llamacloud)
  • GitHub Check: typescript (18, 3.11, ubuntu-22.04, nextjs, --example-file)
  • GitHub Check: typescript (18, 3.11, ubuntu-22.04, nextjs, --no-files)
  • GitHub Check: typescript (18, 3.11, windows-latest, nextjs, --llamacloud)
  • GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --example-file)
  • GitHub Check: typescript (18, 3.11, windows-latest, nextjs, --example-file)
  • GitHub Check: typescript (18, 3.11, windows-latest, nextjs, --no-files)
  • GitHub Check: python (20, 3.11, windows-latest, fastapi, --llamacloud)
  • GitHub Check: python (20, 3.11, windows-latest, fastapi, --example-file)
  • GitHub Check: typescript (18, 3.11, macos-latest, nextjs, --example-file)
  • GitHub Check: python (20, 3.11, windows-latest, fastapi, --no-files)
  • GitHub Check: typescript (18, 3.11, macos-latest, nextjs, --no-files)
  • GitHub Check: python (20, 3.11, macos-latest, fastapi, --example-file)
🔇 Additional comments (1)
llama-index-server/README.md (1)

79-83: Updated UIConfig Documentation:
The configuration options section now clearly outlines the structure of the new ui_config parameter, listing keys such as enabled, app_title, starter_questions, and ui_path. This update improves clarity. Please verify that the documented default values match the implementation, and consider adding example default values if they differ from what users might expect.

@marcusschiesser marcusschiesser moved this to In Progress in Framework Apr 3, 2025
@leehuwuj leehuwuj changed the title chore: simplify local index and add ui config chore: simplify local index code Apr 3, 2025
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0c7262d and ab1127c.

📒 Files selected for processing (2)
  • templates/types/llamaindexserver/fastapi/app/index.py (1 hunks)
  • templates/types/llamaindexserver/fastapi/generate.py (2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
`templates/**`: For files under the `templates` folder, do not report 'Missing Dependencies Detected' errors.

templates/**: For files under the templates folder, do not report 'Missing Dependencies Detected' errors.

  • templates/types/llamaindexserver/fastapi/app/index.py
  • templates/types/llamaindexserver/fastapi/generate.py
🧬 Code Definitions (1)
templates/types/llamaindexserver/fastapi/generate.py (1)
templates/types/llamaindexserver/fastapi/app/settings.py (1)
  • init_settings (6-8)
⏰ Context from checks skipped due to timeout of 90000ms (28)
  • GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --llamacloud)
  • GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --example-file)
  • GitHub Check: typescript (20, 3.11, ubuntu-22.04, nextjs, --no-files)
  • GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --llamacloud)
  • GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --example-file)
  • GitHub Check: typescript (20, 3.11, windows-latest, nextjs, --no-files)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --llamacloud)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --example-file)
  • GitHub Check: typescript (20, 3.11, macos-latest, nextjs, --no-files)
  • GitHub Check: typescript (18, 3.11, ubuntu-22.04, nextjs, --llamacloud)
  • GitHub Check: typescript (18, 3.11, ubuntu-22.04, nextjs, --example-file)
  • GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --llamacloud)
  • GitHub Check: typescript (18, 3.11, ubuntu-22.04, nextjs, --no-files)
  • GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --example-file)
  • GitHub Check: typescript (18, 3.11, windows-latest, nextjs, --llamacloud)
  • GitHub Check: python (20, 3.11, ubuntu-22.04, fastapi, --no-files)
  • GitHub Check: typescript (18, 3.11, windows-latest, nextjs, --example-file)
  • GitHub Check: python (20, 3.11, windows-latest, fastapi, --llamacloud)
  • GitHub Check: typescript (18, 3.11, windows-latest, nextjs, --no-files)
  • GitHub Check: python (20, 3.11, windows-latest, fastapi, --example-file)
  • GitHub Check: typescript (18, 3.11, macos-latest, nextjs, --llamacloud)
  • GitHub Check: python (20, 3.11, windows-latest, fastapi, --no-files)
  • GitHub Check: typescript (18, 3.11, macos-latest, nextjs, --example-file)
  • GitHub Check: python (20, 3.11, macos-latest, fastapi, --llamacloud)
  • GitHub Check: typescript (18, 3.11, macos-latest, nextjs, --no-files)
  • GitHub Check: Unit Tests (windows-latest, 3.9)
  • GitHub Check: python (20, 3.11, macos-latest, fastapi, --example-file)
  • GitHub Check: python (20, 3.11, macos-latest, fastapi, --no-files)
🔇 Additional comments (3)
templates/types/llamaindexserver/fastapi/generate.py (1)

4-4: Good job on simplifying the import!

Importing the constant STORAGE_DIR from app.index makes the code more consistent and simplifies maintenance.

templates/types/llamaindexserver/fastapi/app/index.py (2)

11-11: Good simplification with STORAGE_DIR constant.

Using a constant instead of a class with a single attribute simplifies the code while maintaining the functionality. This aligns well with the PR objective to simplify the local index code.


16-16: Successfully refactored to use STORAGE_DIR throughout the code.

You've consistently replaced all references to the previous IndexConfig class with the new STORAGE_DIR constant, ensuring the code remains functional and easier to understand.

While this change reduces the flexibility of configuring the storage directory at runtime, it aligns with the goal of simplifying the code and makes the behavior more predictable.

Also applies to: 19-23

@marcusschiesser marcusschiesser merged commit 08b3e07 into main Apr 3, 2025
33 checks passed
@github-project-automation github-project-automation bot moved this from In Progress to Done in Framework Apr 3, 2025
@marcusschiesser marcusschiesser deleted the lee/post-release-enhancement branch April 3, 2025 12:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

3 participants