We could move the license logic from the config files (package.json etc.) to searching for the actual license file.
So in the README, we can be sure to report the correct license with also the link to the file in the repo
[x] Rethink logic where to put assemble_license. Flow: converter -> merger -> assembler
[x] Build the logic to put the right license: if fond the file and is not github repo, in that case seek for keywords in the file to detect the right license
Config files are loaded with the license information.
One method checks if there is a license file inside the repo, if there is then I check if the repo is github, if so I put link, otherwise I search the found file for keywords to find the correct license
if in the merger all ConverterOutput have no license then I propose to the user to choose one, and once chosen we also create the file in the root of the repository
We could move the license logic from the config files (package.json etc.) to searching for the actual license file. So in the README, we can be sure to report the correct license with also the link to the file in the repo