Repository navigation
Conversation
Co-authored by AI (GPT-5)
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.
WHY are these changes introduced?
Add historical app-log retrieval behind a hidden command, leaving existing commands unchanged.
WHAT is this pull request doing?
Adds
shopify app logs-nextwith webhook/GraphQL filters, existing user authentication, and table/JSON output.JSON starts with only
logs,ordering, andlimitations. It preserves native record fields and deliberately omitsqueryand the conventionalpageInfo: neither is required for this initial retrieval workflow, and metadata can be added later without committing to pagination now.How to manually test your changes?
Retrieval requires App Logs API access. Confirm
app --helphideslogs-nextand existingapp logs/app logs sourcesremain available.Checklist
Co-authored by AI (GPT-5)