For now, I am considering using the following specifications for file loading.
- only one file can be loaded
- specify only the folder name from the .env file
- automatically read json files that exist in the specified folder name
Problem
With this method, if there are multiple json files in the specified folder, the intended file cannot be read. For example,
In such a case, it is not possible to explicitly set whether a.json or b.json is to be read.
Solution
As before, I will allow users to select not only specific folders but also multiple files.
This will enable the library to support the upload of multiple files while maintaining backward compatibility.
For now, I am considering using the following specifications for file loading.
Problem
With this method, if there are multiple json files in the specified folder, the intended file cannot be read. For example,
env file
DATA_DIR=. /hoge
Directory structure
/root
┣ /hoge
┃ ┣ a.json
┃ ┗ b.json
┗ .env
In such a case, it is not possible to explicitly set whether a.json or b.json is to be read.
Solution
As before, I will allow users to select not only specific folders but also multiple files.
This will enable the library to support the upload of multiple files while maintaining backward compatibility.