Model ~/.metanorma/config.yml with LutaML

[ribose-jeffreylau]

Metanorma PR checklist

• Breaking changes (list related PRs)
• Documentation update required (create task for this)
• External dependency introduced (documentation update need)
• Gem with native library introduced

Fixes #365

[ronaldtse]

LGTM

[ribose-jeffreylau]

This actually is not as straightforward as initially thought.

Currently, the config Hash is being manipulated with .merge (in multiple places) and is then passed to Metanorma::Compile:

metanorma-cli/lib/metanorma/cli/site_generator.rb

Lines 91 to 97 in 77bbccd

	options = @compile_options.merge(
	format: :asciidoc, output_dir: build_asset_output_directory(source),
	site_generate: true
	)
	options[:baseassetpath] = Pathname.new(source.to_s).dirname.to_s
	Metanorma::Cli::Compiler.compile(source.to_s, options)

Not sure how best to handle mutations to a LutaML model for now...

[ronaldtse]

This thing is not supposed to be manipulated after. The merges are just used to set defaults or additional things, they can be easily changed to method setters. Now being a lutaml-model we can set those things earlier on and can also allow the user to set them in the config, which is a great feature.

[opoudjis]

@ribose-jeffreylau @ronaldtse This PR has been unactioned for six months. Is it still to be fixed?

[opoudjis]

@ribose-jeffreylau @ronaldtse Update on this please. Metanorma is being plagued by PRs sitting unactioned for months.

[opoudjis]

@ronaldtse @ribose-jeffreylau This has now been sitting unactioned for a full year. If I do not hear back from either of you in the next week, I will be closing this PR.