Open jribbink opened 3 months ago
FCL would greatly benefit from nested config values.
I.e.
fcl.config.get("foo") // {"bar": 123, "baz": 456} // where "foo.bar" = 123 & "foo.baz" = 456
This would also streamline setting configuration:
fcl.config({ foo: { bar: 123, baz: 456 } })
as users can now treat their configuration as a nested hierarchy instead of a flat map of values.
For backward-compatibility, both formats should be supported still.
No response
Issue to be solved
FCL would greatly benefit from nested config values.
I.e.
This would also streamline setting configuration:
as users can now treat their configuration as a nested hierarchy instead of a flat map of values.
For backward-compatibility, both formats should be supported still.
Suggest A Solution
No response
What are you currently working on that this is blocking?
No response