tencent/westore

小程序MVVM分层架构

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 47 minutes ago
Added to GitGenius on September 16th, 2026
Created on May 7th, 2015
Open Issues & Pull Requests: 63 (+0)
GitHub issues: Enabled
Number of forks: 478
Total Stargazers: 4,281 (+0)
Total Subscribers: 147 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 499.5 days
Mean response time: 316.3 days
90th percentile: 660.7 days
Tracked items: 7

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 6
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,374 days
Stale 30+ days: 6
Stale 90+ days: 6

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Westore is a state management framework for mini-programs that implements an MVVM layered architecture.

The framework addresses the challenge of managing application state in mini-programs, where direct manipulation of component data can become unwieldy as complexity grows. Westore provides a centralized store pattern where application state is managed separately from view components. It uses a diff-based approach to detect state changes and automatically update only the affected parts of the UI, reducing unnecessary re-renders and improving performance. The architecture separates concerns into model, view, and view-model layers, allowing developers to organize business logic independently from presentation logic.

Westore is suited for mini-program developers building applications with non-trivial state management needs. The framework is particularly valuable when applications require shared state across multiple components or when state changes need to trigger coordinated updates across the UI. It works well for projects where performance optimization through selective updates matters, since the diff mechanism avoids broadcasting entire state objects to components on every change. Developers accustomed to MVVM patterns from other frameworks will find the architectural approach familiar.

The project shows consistent maintenance activity with regular updates addressing bug fixes and feature improvements. The codebase demonstrates active refinement of the core diff and state update mechanisms. Development includes ongoing work to optimize the performance characteristics of state synchronization. The project maintains responsiveness to issues and pull requests from the community. Documentation and examples receive periodic updates to reflect changes in the framework's capabilities.