-
-
Notifications
You must be signed in to change notification settings - Fork 101
Add --recurse mode to fedify lookup and fix separator output
#608
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
46 commits
Select commit
Hold shift + click to select a range
23574ef
Add recurse mode and fix lookup separators
dahlia cd5c522
Validate lookup.recurseDepth config as positive integer
dahlia 10b30f4
Correct lookup docs for traverse/recurse multi-argument behavior
dahlia ee07874
Print exactly one separator between printed lookup objects
dahlia acec2d3
Reuse output stream across lookup multi-object writes
dahlia d418286
Avoid poisoning visited set on suppressed lookup failures
dahlia 280502b
Simplify recursive target resolver for validated recurse props
dahlia 7bb5605
Fix recurse visited scope and output separator destination
dahlia d9e97d2
Block recursive private-address fetches in lookup
dahlia 8ee7f87
Use strict loader for recursive lookup network fetches
dahlia 5f3fd7a
Write separators to the configured lookup output
dahlia af550c2
Block private-address image fetches in lookup rendering
dahlia b27d76a
Isolate docloader cache keys by network policy
dahlia 1db0a8b
Simplify image download error handling in lookup
dahlia 5e3be4a
Support quoteUrl recursion targets in lookup
dahlia 77c8e7e
Let Optique show recurse choices in help output
dahlia 4f24401
Lazily initialize recurse-only document loaders
dahlia 9fa76c7
Apply authorized fetch to recursive follow-up lookups
dahlia ff23875
Await stdout backpressure in writeSeparator
dahlia 21b087e
Handle stream error events in lookup output
dahlia c6851fa
Lazily create runLookup output stream
dahlia e09a2a4
Handle recurse output write failures safely
dahlia 1248f71
Guard multi-object output writes in lookup
dahlia 09d2338
Align recurse rendering with strict context policy
dahlia 204cdc6
Harden stream error handling in lookup output
dahlia dfce3fb
Apply strict URL policy in recurse lookups
dahlia a66d613
Deduplicate suppress-errors option definition
dahlia 005c4c5
Always exit in finalizeAndExit cleanup path
dahlia 933784d
Remove redundant recurse URL pre-validation
dahlia 12ebc6f
Handle sync stream throw paths in lookup output helpers
dahlia 442f1d5
Harden lookup output destination and finalization paths
dahlia 9400c07
Tighten lookup loader safety and document public helpers
dahlia ee934f5
Harden lookup private-address handling and image redirects
dahlia 5101c9c
Fix recurse private-address handling in authorized fetch mode
dahlia 8f1d18b
Improve suppressed recurse diagnostics and output/body error handling
dahlia 3c7eb9b
Scope private-address default, cleanup exit status, and deterministic…
dahlia 95423d9
Harden image temp path extension handling
dahlia 764e68d
Make recursive target mapping explicit for quote properties
dahlia aab372f
Clarify private-address policy for recursive lookup docs
dahlia f00210c
Improve lookup hints for private-address validation failures
dahlia b898148
Use switch-based recursion property mapping
dahlia da6a6fc
Fix lookup failure hint classification and suppression logic
dahlia 9303408
Harden CLI document loader defaults against private-address access
dahlia 7a05536
Handle extensionless image URLs in downloadImage safely
dahlia e859672
Keep private-address hints visible with authorized fetch enabled
dahlia d3737a8
Support extensionless nested image URLs in downloadImage
dahlia File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,15 @@ | ||
| import assert from "node:assert/strict"; | ||
| import test from "node:test"; | ||
| import { getDocumentLoaderCachePrefix } from "./docloader.ts"; | ||
|
|
||
| test("getDocumentLoaderCachePrefix - isolates strict and permissive policies", () => { | ||
| const strictPrefix = getDocumentLoaderCachePrefix("fedify-cli", false); | ||
| const permissivePrefix = getDocumentLoaderCachePrefix("fedify-cli", true); | ||
| assert.notDeepEqual(strictPrefix, permissivePrefix); | ||
| }); | ||
|
|
||
| test("getDocumentLoaderCachePrefix - includes user agent namespace", () => { | ||
| const prefixA = getDocumentLoaderCachePrefix("agent-a", false); | ||
| const prefixB = getDocumentLoaderCachePrefix("agent-b", false); | ||
| assert.notDeepEqual(prefixA, prefixB); | ||
| }); |
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.