Skip to content

Conversation

@nielsneerhoff
Copy link
Member

Resources showing that interactive IO operations do not fit the IO abstraction of Ordeq.
Interactive IO operations like chatting, running a subprocess and making an API request:

  • do roughly the same operation on read and write (e.g. ollama.chat, requests.request)
  • produce data in this operation that may be needed in other nodes (therefore this cannot be done in an IO's save)

The resources are intentionally ill-designed, to show the need for documenting the best practices for users of Ordeq with interactive IO.

@nielsneerhoff nielsneerhoff added the internal Non-functional changes label Dec 10, 2025
@nielsneerhoff nielsneerhoff enabled auto-merge (squash) December 10, 2025 13:36
@nielsneerhoff nielsneerhoff merged commit ef32427 into main Dec 10, 2025
41 checks passed
@nielsneerhoff nielsneerhoff deleted the interactive-ios branch December 10, 2025 16:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

internal Non-functional changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants