Access custom config array throughout session

[ashmaroli]

Resolves #6180
Instead of having the array of custom configs removed, let it be available throughout current session.

Specific Use Case:

Allow Jekyll Admin to determine which config file to re-read if not the default _config.yml or _config.yaml

/cc @jekyll/ecosystem @parkr

[parkr]

I dig the idea.

Three things: (1) when config is empty/has an empty string like above, as checked in the line directly after the one you change, let's fill that in with whatever file we read by default; (2) let's add a test; (3) let's not expose this in liquid yet, so create a no-op method in SiteDrop called config.

[ashmaroli]

Three things: (1) when config is empty/has an empty string like above, as checked in the line directly after the one you change, let's fill that in with whatever file we read by default; (2) let's add a test; (3) let's not expose this in liquid yet, so create a no-op method in SiteDrop called config.

(1) Isn't that how it is already? If config_files is an empty array, proceed to look for default config file(s)
(2) Fixing failing tests do produce enough results asserting the changed behavior, no clear on what else needs to be tested..
(3) Implemented with an empty #config

@parkr

[ashmaroli]

Hi, Any other changes to be made?

[ghost]

this looks good to me

[ashmaroli]

👍 Thanks Olivia

[parkr]

👏

@jekyllbot: merge +minor