Skip to content
This repository was archived by the owner on Feb 12, 2024. It is now read-only.
This repository was archived by the owner on Feb 12, 2024. It is now read-only.

Streamlining IPFS Config  #3390

@Gozala

Description

@Gozala

#3365 spawned discussions around config. I think deserves a separate conversation and possibly pull request based on consensus.

Right now there are various assumptions made about the config across the code base e.g.

  • Some code paths assume that config will have certain properties e.g. Addresses or Discovery.
  • Other code paths assume that it my not have anything at all.
  • Some other code paths assume that merging incomplete config with some other (possibly invalid / incomplete config e.g read from file) will result in complete config.

All this makes it very difficult to encode invariants in type checker and uphold them as well. I would like to propose isolating the config parsing, merging access with defaults etc... into separate module that deals with all this so all the code paths can be be free of those concerns and be valid.

Metadata

Metadata

Assignees

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions