API for RakuDoc v2 about problem-solving

[finanalyst]

My proposal would be for:

• directives (there is a list of names) to be placed in a RakuAST::Doc::Directive node
  • the name field/attribute would be the directive name
  • meta would contain any metadata option associated with the directive
  • object would contain the first argument
  • predicate would contain the second one
• markup codes (no change from current RakuAST::Doc::Markup)
• blocks to be placed in a RakuAST::Doc::Block node
  • 'name' contains the block name
  • 'type' contains 'built-in', 'custom', 'semantic'
  • 'meta' to contain meta options
  • 'contents' to contain the block contents

Currently, RakuAST provides a RakuAST::Doc::DeclaratorTarget node for the declarator blocks, which is consistent with the code/text distinction.

If this code/text distinction is carried through to the API, then there should be separate nodes for the =finished directive and =data block.

[lizmat]

Closing, since the discussion is in now in https://github.com/Raku/RakuDoc-GAMMA . Please re-open if you disagree.