Skip to content
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

✨ feat: add support for application state management #3360

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

efectn
Copy link
Member

@efectn efectn commented Mar 18, 2025

Description

This PR adds support for basic state management like FastAPI to Fiber using sync.Map.

Fixes #3077

Changes introduced

List the new features or adjustments introduced in this pull request. Provide details on benchmarks, documentation updates, changelog entries, and if applicable, the migration guide.

  • Benchmarks: Describe any performance benchmarks and improvements related to the changes.
  • Documentation Update: Detail the updates made to the documentation and links to the changed files.
  • Changelog/What's New: Include a summary of the additions for the upcoming release notes.
  • Migration Guide: If necessary, provide a guide or steps for users to migrate their existing code to accommodate these changes.
  • API Alignment with Express: Explain how the changes align with the Express API.
  • API Longevity: Discuss the steps taken to ensure that the new or updated APIs are consistent and not prone to breaking changes.
  • Examples: Provide examples demonstrating the new features or changes in action.

Type of change

Please delete options that are not relevant.

  • New feature (non-breaking change which adds functionality)
  • Enhancement (improvement to existing features and functionality)
  • Documentation update (changes to documentation)
  • Performance improvement (non-breaking change which improves efficiency)
  • Code consistency (non-breaking change which improves code reliability and robustness)

Checklist

Before you submit your pull request, please make sure you meet these requirements:

  • Followed the inspiration of the Express.js framework for new functionalities, making them similar in usage.
  • Conducted a self-review of the code and provided comments for complex or critical parts.
  • Updated the documentation in the /docs/ directory for Fiber's documentation.
  • Added or updated unit tests to validate the effectiveness of the changes or new features.
  • Ensured that new and existing unit tests pass locally with the changes.
  • Verified that any new dependencies are essential and have been agreed upon by the maintainers/community.
  • Aimed for optimal performance with minimal allocations in the new code.
  • Provided benchmarks for the new code to analyze and improve upon.

Commit formatting

Please use emojis in commit messages for an easy way to identify the purpose or intention of a commit. Check out the emoji cheatsheet here: CONTRIBUTING.md

@efectn efectn requested a review from a team as a code owner March 18, 2025 18:40
@efectn efectn requested review from gaby, sixcolors and ReneWerner87 and removed request for a team March 18, 2025 18:40
Copy link
Contributor

coderabbitai bot commented Mar 18, 2025

Warning

Rate limit exceeded

@efectn has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 2 minutes and 29 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 95f0eec and 804e8f8.

📒 Files selected for processing (2)
  • docs/api/state.md (1 hunks)
  • state_test.go (1 hunks)

Walkthrough

This PR introduces application state management features by adding a new state field and a corresponding accessor method (State()) to the App struct. A new State struct, implemented as a thread-safe key-value store, is added along with numerous utility methods for setting, retrieving, and managing state. Complementing these changes, comprehensive tests and benchmarks validate the functionality and performance of the state management system. Additionally, a minor comment correction in the Config struct improves documentation clarity.

Changes

File(s) Change Summary
app.go Added a new state *State field to the App struct and a corresponding State() method for accessing it. Also corrected a comment typo for the StrictRouting field in the Config struct.
state.go Introduced a new State struct implemented as a thread-safe key-value store. Added methods for state creation (newState), setting and retrieving values (Set, Get, GetString, GetInt, GetBool, GetFloat64), error-handling retrieval (MustGet), deletion (Delete), clearing (Reset), key enumeration (Keys), length (Len), and generic retrieval (GetState, MustGetState, GetStateWithDefault).
app_test.go Added Test_App_State to verify that state can be set and retrieved correctly on an App instance.
state_test.go Added comprehensive unit tests and benchmarks covering all methods of the State struct, ensuring correct functionality for value setting, retrieval (including type-specific and generic functions), deletion, clearing, and performance under load.
docs/api/constants.md Modified the sidebar_position attribute from 8 to 9 in the metadata section.
docs/api/state.md Introduced a new document detailing the state management functionality, including the State struct and its methods, along with usage examples.
docs/whats_new.md Added a new entry for the State method in the "New Methods" section, describing its purpose and linking to the detailed documentation.

Sequence Diagram(s)

sequenceDiagram
    participant C as Client/Test
    participant A as App
    participant S as State
    C->>A: Call State() to access state
    A->>S: [State accessor] invoked
    Note over S: Set/Update operations in State
    C->>A: Call app.State().Set("key", "value")
    A->>S: Execute Set("key", "value")
    S-->>A: Acknowledge the set operation
    C->>A: Call app.State().GetString("key")
    A->>S: Execute Get("key")
    S-->>A: Return "value" and status ok
    A-->>C: Return "value"
Loading

Assessment against linked issues

Objective Addressed Explanation
Application State Management & Middleware Integration ([#3077])
Ease of Use: Simple, Intuitive API for state handling ([#3077])
Performance & Concurrency: Thread-safe and benchmarked ([#3077])

Suggested labels

✏️ Feature, v3

Suggested reviewers

  • gaby
  • sixcolors
  • ReneWerner87

Poem

I'm a rabbit with a hop so light,
Coding through state fields day and night.
Carrots and code twirl in playful delight,
With benchmarks and tests keeping all things right.
A hoppy change leads our app to new flight! 🥕


Note

🎁 Summarized by CodeRabbit Free

Your organization has reached its limit of developer seats under the Pro Plan. For new users, CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please add seats to your subscription by visiting https://app.coderabbit.ai/login.If you believe this is a mistake and have available seats, please assign one to the pull request author through the subscription management page using the link above.

🪧 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 resolve resolve all the CodeRabbit review comments.
  • @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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

Copy link

codecov bot commented Mar 18, 2025

Codecov Report

Attention: Patch coverage is 96.66667% with 3 lines in your changes missing coverage. Please review.

Project coverage is 83.83%. Comparing base (395c8fa) to head (804e8f8).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
state.go 96.47% 2 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3360      +/-   ##
==========================================
+ Coverage   83.61%   83.83%   +0.21%     
==========================================
  Files         118      119       +1     
  Lines       11727    11818      +91     
==========================================
+ Hits         9806     9908     +102     
+ Misses       1491     1483       -8     
+ Partials      430      427       -3     
Flag Coverage Δ
unittests 83.83% <96.66%> (+0.21%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Contributor

@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 (7)
app.go (1)

143-143: Fix typo in comment.

There's a typo in the comment for StrictRouting - "Ftrue" should be "true".

-	// When set to Ftrue, the router treats "/foo" and "/foo/" as different.
+	// When set to true, the router treats "/foo" and "/foo/" as different.
state.go (3)

81-84: Fix method comment.

The method comment incorrectly describes this as "MustGetString" but the method is actually "Delete".

-// MustGetString retrieves a string value from the State and panics if the key is not found.
+// Delete removes a key-value pair from the State.

86-89: Fix method comment.

The method comment incorrectly describes this as "Reset" but the method is actually "Clear".

-// Reset resets the State.
+// Clear removes all key-value pairs from the State.

91-100: Add error handling for key type assertion.

The Keys method assumes all keys are strings, but there's no error handling for the type assertion. This could potentially cause a panic if a non-string key was somehow stored in the map.

func (s *State) Keys() []string {
	keys := make([]string, 0)
	s.dependencies.Range(func(key, _ any) bool {
-		keys = append(keys, key.(string))
+		if keyStr, ok := key.(string); ok {
+			keys = append(keys, keyStr)
+		}
		return true
	})

	return keys
}
🧰 Tools
🪛 GitHub Check: lint

[failure] 95-95:
Error return value is not checked (errcheck)

state_test.go (3)

153-159: Optimize struct field alignment.

The testCase struct could be optimized for memory efficiency by reordering fields.

type testCase[T any] struct {
-	name     string
-	key      string
-	value    any
-	expected T
-	ok       bool
+	expected T
+	value    any
+	name     string
+	key      string
+	ok       bool
}
🧰 Tools
🪛 GitHub Check: lint

[failure] 153-153:
fieldalignment: struct with 64 pointer bytes could be 56 (govet)


161-169: Add t.Helper() to test helper function.

The runGenericTest function should start with t.Helper() to improve test output when this helper fails.

func runGenericTest[T any](t *testing.T, getter func(*State, string) (T, bool), tests []testCase[T]) {
+	t.Helper()
	st := newState()
	for _, tc := range tests {
		st.Set(tc.key, tc.value)
		got, ok := getter(st, tc.key)
		require.Equal(t, tc.ok, ok, tc.name)
		require.Equal(t, tc.expected, got, tc.name)
	}
}
🧰 Tools
🪛 GitHub Check: lint

[failure] 161-161:
test helper function should start from t.Helper() (thelper)


73-87: Use require.InDelta for floating point comparisons.

When comparing floating point values, it's better to use require.InDelta or require.InEpsilon instead of require.Equal to handle potential floating point precision issues.

func TestState_GetFloat64(t *testing.T) {
	t.Parallel()
	st := newState()

	st.Set("pi", 3.14)
	f, ok := st.GetFloat64("pi")
	require.True(t, ok)
-	require.Equal(t, 3.14, f)
+	require.InDelta(t, 3.14, f, 0.0001)

	// wrong type should return zero value
	st.Set("int", 10)
	f, ok = st.GetFloat64("int")
	require.False(t, ok)
-	require.Equal(t, 0.0, f)
+	require.InDelta(t, 0.0, f, 0.0001)
}
🧰 Tools
🪛 GitHub Check: lint

[failure] 86-86:
float-compare: use require.InEpsilon (or InDelta) (testifylint)


[failure] 80-80:
float-compare: use require.InEpsilon (or InDelta) (testifylint)

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 395c8fa and 655677e.

📒 Files selected for processing (4)
  • app.go (4 hunks)
  • app_test.go (1 hunks)
  • state.go (1 hunks)
  • state_test.go (1 hunks)
🧰 Additional context used
🪛 GitHub Actions: golangci-lint
app.go

[error] 90-90: fieldalignment: struct with 1304 pointer bytes could be 1232 (govet)

🪛 GitHub Check: codecov/patch
state.go

[warning] 36-36: state.go#L36
Added line #L36 was not covered by tests


[warning] 47-47: state.go#L47
Added line #L47 was not covered by tests


[warning] 58-58: state.go#L58
Added line #L58 was not covered by tests


[warning] 69-69: state.go#L69
Added line #L69 was not covered by tests

🪛 GitHub Check: lint
state.go

[failure] 95-95:
Error return value is not checked (errcheck)


[failure] 51-51:
confusing-results: unnamed results of the same type may be confusing, consider using named results (revive)


[failure] 3-3:
should only use grouped 'import' declarations (grouper)

state_test.go

[failure] 161-161:
test helper function should start from t.Helper() (thelper)


[failure] 153-153:
fieldalignment: struct with 64 pointer bytes could be 56 (govet)


[failure] 86-86:
float-compare: use require.InEpsilon (or InDelta) (testifylint)


[failure] 80-80:
float-compare: use require.InEpsilon (or InDelta) (testifylint)

⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: Compare
  • GitHub Check: unit (1.23.x, windows-latest)
  • GitHub Check: unit (1.24.x, windows-latest)
  • GitHub Check: repeated
🔇 Additional comments (11)
app_test.go (1)

1893-1901: LGTM! Good test for the new state functionality.

The test correctly verifies the basic state management functionality by setting and retrieving a value, ensuring the expected behavior works as intended.

app.go (3)

132-133: LGTM! Good addition of the state field.

Adding the state field to the App struct is a clean way to implement application-wide state management capabilities.


520-522: LGTM! Proper state initialization.

The state is properly initialized during app creation, ensuring it's always available.


960-963: LGTM! Clean accessor method implementation.

The State() method provides a clean interface for accessing the app's state from handlers.

state.go (5)

5-9: LGTM! Good use of sync.Map for thread-safety.

Using sync.Map is a solid choice for the state implementation, as it provides built-in thread safety for concurrent access without manual locking.


11-26: LGTM! Clean implementation of core state functionality.

The newState function and basic Set/Get methods are well-implemented with a clean API.


28-70: LGTM! Good implementation of type-specific getters.

The type-specific getters (GetString, GetInt, GetBool, GetFloat64) follow a consistent pattern and properly handle type mismatches by returning false when the type doesn't match.

🧰 Tools
🪛 GitHub Check: codecov/patch

[warning] 36-36: state.go#L36
Added line #L36 was not covered by tests


[warning] 47-47: state.go#L47
Added line #L47 was not covered by tests


[warning] 58-58: state.go#L58
Added line #L58 was not covered by tests


[warning] 69-69: state.go#L69
Added line #L69 was not covered by tests

🪛 GitHub Check: lint

[failure] 51-51:
confusing-results: unnamed results of the same type may be confusing, consider using named results (revive)


72-79: LGTM! Good implementation of MustGet.

The MustGet method provides a convenient way to retrieve a value when the caller knows the key exists, with appropriate panic behavior for missing keys.


102-134: LGTM! Good implementation of helper methods and generic functions.

The Len method and generic GetState/MustGetState functions provide a complete API for state management. The generic functions are particularly useful for type-safe state access.

state_test.go (2)

10-101: LGTM! Comprehensive test coverage.

The tests thoroughly cover the basic state operations, including setting, getting, type mismatches, and error conditions.

🧰 Tools
🪛 GitHub Check: lint

[failure] 86-86:
float-compare: use require.InEpsilon (or InDelta) (testifylint)


[failure] 80-80:
float-compare: use require.InEpsilon (or InDelta) (testifylint)


171-423: LGTM! Excellent test coverage with benchmarks.

The comprehensive test suite covers normal usage, edge cases, and includes benchmarks to ensure performance. The generic tests are particularly valuable for ensuring type safety across different data types.

@efectn efectn added this to the v3 milestone Mar 18, 2025
Copy link
Contributor

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

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

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 1.50.

Benchmark suite Current: 804e8f8 Previous: 87f3f0c Ratio
Benchmark_Ctx_SendString_B 15.64 ns/op 0 B/op 0 allocs/op 9.379 ns/op 0 B/op 0 allocs/op 1.67
Benchmark_Ctx_SendString_B - ns/op 15.64 ns/op 9.379 ns/op 1.67

This comment was automatically generated by workflow using github-action-benchmark.


// Keys retrieves all the keys from the State.
func (s *State) Keys() []string {
keys := make([]string, 0)
Copy link
Member Author

@efectn efectn Mar 18, 2025

Choose a reason for hiding this comment

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

Here we can preallocate the keys slice using s.Len() to reduce the memory allocation; however, it will make the method a little bit slower.

@gaby gaby added the v3 label Mar 19, 2025
@gaby
Copy link
Member

gaby commented Mar 19, 2025

Analysis created by OpenAI: o3-mini-high:

Analysis of the Implementation

1. Thread Safety and Usage of sync.Map

  • The implementation uses Go’s built-in sync.Map to ensure thread safety, which is appropriate for a global key-value store accessed by multiple goroutines concurrently.

2. Naming and Exporting

  • The constructor is named newState (lowercase), which makes it unexported. If the intention is to allow external packages to create a State instance, the constructor should be exported (e.g., NewState).
  • The State type is exported, so providing an exported constructor would improve consistency.

3. Clear Method Implementation

  • The current Clear method calls s.dependencies.Clear(). However, Go’s sync.Map does not provide a Clear method. A proper implementation would iterate over all keys and delete them individually.

4. Generic Get Methods

  • The functions GetState[T] and MustGetState[T] are implemented as package-level functions. It would be more idiomatic to attach these as methods on the State type for improved usability.

5. Additional Convenience Methods

  • A method like Has(key string) bool could simplify checks for the existence of a key.
  • A "get with default" method might be useful in scenarios where you want to provide a fallback value without panicking.

6. Error Handling Philosophy

  • The “MustGet” style panics if a dependency is missing. While this is acceptable in some cases, offering an alternative that returns an error could be more appropriate for production-level code.

Summary of Improvements

  • Exported Constructor: Change newState to NewState to allow external package instantiation.
  • Manual Clear Implementation: Since sync.Map lacks a native Clear method, implement it by iterating over all keys and deleting them.
  • Generic Methods as Struct Methods: Convert the generic getters into methods attached to the State type for improved consistency and usability.
  • Additional Utility Method: Add a Has method for simple existence checks of keys.

These improvements enhance the usability, consistency, and robustness of the implementation while maintaining the thread safety provided by sync.Map.

Implementation:

package fiber

import (
	"sync"
)

// State is a thread-safe global key-value store for app dependencies.
type State struct {
	dependencies sync.Map
}

// NewState creates and returns a new instance of State.
func NewState() *State {
	return &State{
		dependencies: sync.Map{},
	}
}

// Set sets a key-value pair in the State.
func (s *State) Set(key string, value any) {
	s.dependencies.Store(key, value)
}

// Get retrieves a value from the State.
func (s *State) Get(key string) (any, bool) {
	return s.dependencies.Load(key)
}

// GetString retrieves a string value from the State.
func (s *State) GetString(key string) (string, bool) {
	dep, ok := s.Get(key)
	if ok {
		if depString, okCast := dep.(string); okCast {
			return depString, true
		}
	}
	return "", false
}

// GetInt retrieves an int value from the State.
func (s *State) GetInt(key string) (int, bool) {
	dep, ok := s.Get(key)
	if ok {
		if depInt, okCast := dep.(int); okCast {
			return depInt, true
		}
	}
	return 0, false
}

// GetBool retrieves a bool value from the State.
func (s *State) GetBool(key string) (bool, bool) {
	dep, ok := s.Get(key)
	if ok {
		if depBool, okCast := dep.(bool); okCast {
			return depBool, true
		}
	}
	return false, false
}

// GetFloat64 retrieves a float64 value from the State.
func (s *State) GetFloat64(key string) (float64, bool) {
	dep, ok := s.Get(key)
	if ok {
		if depFloat64, okCast := dep.(float64); okCast {
			return depFloat64, true
		}
	}
	return 0, false
}

// MustGet retrieves a value from the State and panics if the key is not found.
func (s *State) MustGet(key string) any {
	if dep, ok := s.Get(key); ok {
		return dep
	}
	panic("state: dependency not found!")
}

// Delete removes a key from the State.
func (s *State) Delete(key string) {
	s.dependencies.Delete(key)
}

// Clear removes all key-value pairs from the State.
func (s *State) Clear() {
	s.dependencies.Range(func(key, _ any) bool {
		s.dependencies.Delete(key)
		return true
	})
}

// Keys retrieves all the keys from the State.
func (s *State) Keys() []string {
	keys := make([]string, 0)
	s.dependencies.Range(func(key, _ any) bool {
		if keyStr, ok := key.(string); ok {
			keys = append(keys, keyStr)
		}
		return true
	})
	return keys
}

// Len returns the number of dependencies in the State.
func (s *State) Len() int {
	length := 0
	s.dependencies.Range(func(_, _ any) bool {
		length++
		return true
	})
	return length
}

// Has checks if the given key exists in the State.
func (s *State) Has(key string) bool {
	_, ok := s.Get(key)
	return ok
}

// GetState retrieves a value from the State, casting it to the desired type.
func (s *State) GetState[T any](key string) (T, bool) {
	dep, ok := s.Get(key)
	if ok {
		if depT, okCast := dep.(T); okCast {
			return depT, true
		}
	}
	var zeroVal T
	return zeroVal, false
}

// MustGetState retrieves a value from the State, casting it to the desired type.
// It panics if the key is not found.
func (s *State) MustGetState[T any](key string) T {
	val, ok := s.GetState[T](key)
	if !ok {
		panic("state: dependency not found!")
	}
	return val
}

@gaby
Copy link
Member

gaby commented Mar 19, 2025

Here's the implementation for GetWithDefault()

// GetWithDefault retrieves a value from the State, casting it to the desired type.
// If the key is not found or the type assertion fails, it returns the provided default value.
func (s *State) GetWithDefault[T any](key string, defaultValue T) T {
	if val, ok := s.Get(key); ok {
		if typed, ok := val.(T); ok {
			return typed
		}
	}
	return defaultValue
}

@efectn efectn force-pushed the state-management branch from 95f0eec to 804e8f8 Compare March 19, 2025 12:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

📝 [Proposal]: Support for Application State Management
3 participants