joanvallve / yaml-schema-cpp Goto Github PK

From c++17, std already includes the filesystem package.

This issue has two implications:

• CMake: Handling dependency requirement boost::filesystem depending on the c++ standard.
• C++/preprocessor: Including proper files and namespace of filesystem.

(imported from gitlab. Author: @joansola)

after compilation, the following bin objects are in directory build/ and not /build/bin/ or build/lib/

• cost-example
• libyaml-schema-cpp_example.so
• libyaml-schema-cpp.so
• stage-example
• yaml_template_generator

(copied from Gitlab. Author: @PepMS )

I found the case where I have a base class that requires no parameters or data to be introduced. Thus, its schema is empty.

Still, I'd like to have an empty base schema, which is not allowed now.

Eventually, the base class might have need some parameters and then, I'll have the machinery ready to add these in the empty base schema.

A workaround is to add in the base class a dummy parameter:

dummy:
  mandatory: false
  type: double
  default: 0
  doc: ""

Implement use of expressions differently: taking parameters from other levels and enabling expressions depending on expressions.. etc

Before applying schema, implement a multiple queried evalSchema function that evals expressions that can be evaluated (considering the YAML) and iterate until all expressions can be evaluated. Then, apply schema.

Eigen is actually not needed by the library. It's just another type of parameter that can be specified. We may want to move all Eigen-dependent code to a folder that is optionally compiled if Eigen is found in the system.

(copied from gitlab. Author: @PepMS)

I have the following situation, where I have a non-mandatory with default param_1 specified inside a params family. That is,

params:
    param_1:
      _mandatory: false
      _type: string
      _doc: "doc_1"
      _default: "string_1"

If, in the input yaml file we do not specify (at least) the params: field, the applySchema() breaks. Probably it is because it tries to access the node[params] to apply the default of param_1` but it does not exist.

I think that a good solution for this might be to add the family node name (in this case params) if it does not exist in the input yaml.

(copied from gitlab. Author: @joanvallve)

A useful future feature!