Repository navigation
feat: expand Registry components and harden native integration - #33
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: 53f8386 The changes in this PR will be included in the next version bump. 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 |
|
Important Review skippedToo many files! This PR contains 466 files, which is 366 over the limit of 100. To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to a paid plan to raise the limit. Usage-priced reviews support at most 300 files. ⚙️ Run configuration
⛔ Files ignored due to path filters: 1
📒 Files selected for processing: 466
You can disable this status message by setting the
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. Comment |
daguanren21
marked this pull request as ready for review
October 20, 2026 00:28
Preserve picker drafts, tab instance identity and enabled focus across updates. Fix scoped native host queries and composite interaction behavior. Separate native test identity from portable app source and deliver the canonical compiler patch to standalone consumers. Resolve CSS assets exactly, preserve CSS escaping without a control-character regex, and pin compatible Taro dependencies. Update generated sources, docs and regression coverage. Verify full typecheck, builds, isolated consumers and exports, and serial web/native E2E (74/74, 91/91).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem / goal
Expand the editable Registry with TimeField and FileType for H5 and native consumers, and improve navigation, Agent disclosure, and Signature behavior across both renderers. This also includes native compiler and packaging fixes discovered while exercising the new component demos in WeChat DevTools and on an iPhone.
This PR remains draft because the physical-device checks listed below are incomplete.
Changes and design
VTimeFieldwith minute steps, bounded and overnight ranges, confirmation/cancellation, and parent-owned values; use it in native documentation and Realworld time inputs. An invalid or off-step external value is preserved until a valid confirmation.VFileTypewith local filename/MIME classification and integrate it into Agent attachment lists. Add native AvatarGroup and correct H5 avatar counting through fragments while preserving Fragment key scopes and stateful member identity during reorder/removal.weapp-vite@7.5.0patch that compiles the app shell through Wevu component registration so native slot/provider ownership is installed correctly.Canonical renderer changes stay in
registry/; package/playground/docs projections are generated from those owners. Pure helpers are shared, while rendering and lifecycle code remain target-specific. The large generated diff is part of the source cutover.One integration owner handled generation and validation. Independent component and native/Agent reviews accepted draft delivery after correcting the AvatarGroup key-scope defect and CSS URL matching. Their source review and the executed checks do not close the physical-device gaps below.
Verification
Delivery checks and final review results are recorded separately from the earlier runtime exercises. The reproducible focused package command uses
--dir packagesto avoid discovering historical local worktrees.pnpm check:generated: 857 projections pass;pnpm check:architecture: 557 product source files pass.max=3, member/group reorder, removal and reusable slot fragments.max=3rendered four avatars and mixed component state. Final browser actions exercise generated source with repeated local keys; counts, stateful labels and overflow remain correct after member/group reorder and removal.Previously exercised during implementation:
Physical-device checks still open
10:31while highlighting09/30; later native hierarchy selects10/31. Obtain settled, state-correlated images and investigate if the mismatch persists. It has not been established as a transient frame.An iPhone session produced component interaction evidence, but remote debugging subsequently returned
Remote debug connection lost. A later brief device/home-page read was followed by another disconnect. Simulator, headless, compiler and artifact checks are not substitutes for these remaining device checks.Risks and rollback
The compiler patch is tied to
weapp-vite@7.5.0and must be re-evaluated when that dependency changes. Component relocation changes generated native paths and is covered by closure/conflict/budget contracts. Physical visual/streaming acceptance remains open; no Android or all-profile device certification is claimed.Revert the PR as a unit to keep canonical sources, generated projections, dependency patch and lockfile consistent. No persisted data migration is introduced.