Collaboration diagram for ipfs::ipld::ResolutionState:

Public Member Functions
	ResolutionState (SlashDelimited path_to_resolve, ResponseSemantic semantic, BlockLookup lookup)

SlashDelimited	MyPath () const

SlashDelimited	PathToResolve () const

bool	IsFinalComponent () const

std::string	NextComponent (Client *) const

NodePtr	GetBlock (std::string const &block_key) const

ResolutionState	WithPath (std::string_view) const

ResolutionState	RestartResolvedPath () const

ResponseSemantic	Semantic () const

void	Descend ()

Constructor & Destructor Documentation

◆ ResolutionState()

ipfs::ipld::ResolutionState::ResolutionState	(	SlashDelimited	path_to_resolve,
		ResponseSemantic	semantic,
		BlockLookup	lookup
	)

Construct from starting info

Parameters

path_to_resolve	Relative to the node resolve is being called on
semantic	If the resolution results in a stem, i.e. a directory-like not a file, would the preference be for a listing preview HTML page -OR- JSON that describes the links to files and CIDs to merge in with this JSON (in the case of a sharded dir)
lookup	Functor that returns a pointer to a node for a given CID if it's already availabe, nullptr otherwise.

The documentation for this class was generated from the following file: