Skip to content

feat: add DocsFilter read path#375

Open
forshev wants to merge 1 commit into290-docs-filterfrom
290-docs-filter-read-path
Open

feat: add DocsFilter read path#375
forshev wants to merge 1 commit into290-docs-filterfrom
290-docs-filter-read-path

Conversation

@forshev
Copy link
Copy Markdown
Collaborator

@forshev forshev commented Mar 6, 2026

Description

Add read path methods to DocsFilter


  • I have read and followed all requirements in CONTRIBUTING.md;
  • I used LLM/AI assistance to make this pull request;

If you have used LLM/AI assistance please provide model name and full prompt:

Model: {{model-name}}
Prompt: {{prompt}}

@eguguchkin eguguchkin added docs_filter feature New feature or request labels Mar 13, 2026
@eguguchkin eguguchkin added this to the v0.70.0 milestone Mar 16, 2026
@eguguchkin eguguchkin requested review from cheb0 and eguguchkin March 16, 2026 09:42
@forshev forshev force-pushed the 290-docs-filter-read-path branch from 5cb9698 to 7f1ecc3 Compare March 20, 2026 14:21
init bool
}

func NewMergedIterator(a, b node.Node) node.Node {
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how much it is different from nodeOr?

I only see laziness (it doesn't call children's Next on creation, but I'm planning to add it to nodeOr and the other nodes, and there should be no problem adding it in this PR)

Or it's different String() print you need?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs_filter feature New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants