Repository navigation
Add per-package LICENSE, examples, and CHANGELOG for pub.dev compliance - #2
Merged
Merged
Conversation
…dev compliance Each publishable package now carries its own MIT LICENSE, an example/README.md recognized by pana as a usage example, and (for supabase_chat_e2ee) a CHANGELOG. The core package scores 150/160 on pana; the remaining 10 (WASM) is capped by the upstream supabase dependency, which is not WASM-compatible.
Replace the thin 21-line placeholder with complete docs: ChatView and EncryptedChatView usage, lifecycle behavior, per-widget API tables for every exported building block (MessageBubble, MessageComposer, TypingIndicator, EncryptedChatBanner), a custom-layout example, and theming notes.
Console walkthrough of the encryption: identity generation, public-bundle publish, matching safety numbers (MITM check), strict-mode refusing an unverified send, the exact ciphertext the server stores, decryption, a multi-turn Double Ratchet conversation, and a swapped-identity-key rejection.
A CLI walkthrough is expected to print; ignore the lint file-wide so dart analyze stays clean across the workspace.
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
1 participant
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.
Brings every publishable package up to pub.dev / pana standards.
What
supabase_chat_e2ee(the only one missing it).Verified
dart analyze packages→ No issues found (static-analysis gate, 50/50).dart format→ 0 of 48 files changed.panaon the coresupabase_realtime_kit→ 150/160.The 150 vs 160 ceiling
The only lost 10 points is Platform support / WASM:
package:supabase(viastorage_client) is not WASM-compatible, so any library depending on it is capped at 150. Dependency-free libraries reach 160; that is not attainable here without droppingsupabase.The three dependent packages (
supabase_chat,_ui,_e2ee) can't be pana-scored standalone yet because they depend on the unpublished core — pana simulates the pub.dev sandbox and strips path overrides. They inherit the same ~150/160 once published in order:supabase_realtime_kit→supabase_chat→_e2ee/_ui.