Folder name system to Config File or JSON

The folder name system sucks.
when we are literally passing so many configs each time why using the folder system. Also in the folder system we can't pass some characters which are necessary. Like in the concept.

The issue names no files, tests, or entry points. Start by locating the current folder-name configuration handling and how multiple configs are passed; then determine the expected config-file or JSON format and character support. Done means the replacement approach is specified and implemented with coverage for the requested configuration cases.

Written by the indexing model from the issue text.