As config files become more complex, this function becomes more computationally expensive.
Because this function effectively evaluates to the same output everytime for a given hub (unless of course the config changes), it's a good candidate for memoisation, especially for use in a function to validate many files in a hub (#83 )
If implemented, a note in the docs should also be included to alert users that if they make changes to the config in between calls they should refresh their session to clear the cache.
As config files become more complex, this function becomes more computationally expensive.
Because this function effectively evaluates to the same output everytime for a given hub (unless of course the config changes), it's a good candidate for memoisation, especially for use in a function to validate many files in a hub (#83 )
If implemented, a note in the docs should also be included to alert users that if they make changes to the config in between calls they should refresh their session to clear the cache.