You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature Request: Use FRP as a Library and Update samber/lo Dependency
English Summary
Problem:
Currently, the project uses samber/lo as a dependency, but with the release of newer versions, compatibility issues arise when importing and using the library at the code layer. Specifically, samber/lo does not compile with the latest version.
Proposed Solution:
1. Refactor FRP to be more modular, allowing it to be imported as a library in the code layer without additional setup issues.
2. Update the dependency to the latest version of samber/lo and ensure compatibility with the refactored structure.
Benefits:
• Streamlined integration of FRP in projects where it acts as a library.
• Future-proofing against potential versioning issues in samber/lo.
Describe alternatives you've considered
No response
Affected area
Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others
The text was updated successfully, but these errors were encountered:
Describe the feature request
Feature Request: Use FRP as a Library and Update samber/lo Dependency
English Summary
Problem:
Currently, the project uses samber/lo as a dependency, but with the release of newer versions, compatibility issues arise when importing and using the library at the code layer. Specifically, samber/lo does not compile with the latest version.
Proposed Solution:
Benefits:
Describe alternatives you've considered
No response
Affected area
The text was updated successfully, but these errors were encountered: