Repository navigation
Conversation
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.
Create standalone photo collections from the Mini App Create page or Telegram keyboard without event dates, ticket booking or RSVP. Each collection has separate viewer and contributor links, and owners can show or hide uploader names in both interfaces. Hiding names removes attribution from gallery responses, preview labels and bot captions while preserving stored media and uploader records.
Validation: 469 regression tests pass; Worker build, static asset/import checks and mocked D1/Telegram integration pass. Checked creation and link results at a 390 × 844 mobile viewport with no horizontal overflow. Coverage includes role enforcement, stale upload sessions, owner-only visibility settings, idempotent creation, private uploader metadata and existing event behavior.
No database migration is required. Production deployment is performed separately through the CLI with existing variables and secrets preserved.