daco 0.2.0+1

A tool for maintaining Dart comments. Supports formatting of comments, including embedded Dart code.

A tool for maintaining Dart comments (daco).

This package is in an early stage of development. Please file an issue if you find a bug or start a discussion if you have a question.

Getting started

1. Make sure you have a recent version of NodeJS (>=14) installed and on the path. daco uses prettier to format Markdown.

2. Install daco globally:

   dart pub global activate daco
   

3. Format the Dart files within the current directory:

   daco format .
   

Formatting

daco formats Dart files, including documentation comments.

prettier is used to format comments as Markdown. This means that the conventions of prettier are applied, such as using ** to bold text instead of __. A nice feature of prettier is that Markdown tables are pretty-printed.

Prose is reprinted to optimally fit within the specified line length (defaults to 80):

- /// Formats the given [source]   string containing an entire Dart compilation unit.
+ /// Formats the given [source] string containing an entire Dart compilation
+ /// unit.
  Future<String> format(String source, {String? path}) async;

This is useful when writing and updating documentation comments and an edit pushes some text beyond the preferred line length.

Example code in fenced code blocks that is marked as Dart code is formatted:

  /// Greets the user.
  ///
  /// ```dart
- /// greet(name: 'Alice',);
+ /// greet(
+ ///   name: 'Alice',
+ /// );
  /// ```
  void greet({required String name});

Formatting of example code and documentation comments is recursive. That means documentation comments in example code are formatted, too.

The example code is parsed and if it contains syntactic errors they are reported with correct line and column numbers. This provides a basic check, ensuring that the code is at least syntactically correct.

Dartdoc tags

Dartdoc supports tags for features such as templates. Dartdoc tags should be separated from other content with an empty line, since prettier does not recognize them as special and formats them as simple text:

/// A top level constant.
///
/// {@template foo}
///
/// The template content.
///
/// {@endtemplate}
const foo = 'bar';

When formatting a preexisting codebase special attention should be paid to the location of dartdoc tags after formatting.

Example code attributes

Example code can be annotated with attributes to influence how it is processed.

ignore

If example code should not be processed, it can be ignored by annotating it with the ignore attribute.

The example code below, for example, is not valid and would result in an error, but it is instead ignored:

/// Greets the user.
///
/// ```dart ignore
/// greet(name: ...);
/// ```
void greet({required String name});

main

Example code must represent a valid Dart file. Often it is preferable to write example code as if it were contained in a function, but without the function syntax and indentation.

By annotating example code with the main attribute the code is wrapped in a function before processing:

/// Greets the user.
///
/// ```dart main
/// greet(name: 'Alice');
/// ```
void greet({required String name});

TODO

• ❌ Support formatting of end of line comments
• ❌ Support disabling formatting for a comment

Ideas

• Integrate formatting with IDEs
• Analyze comments
  • Spelling
  • Punctuation
• Format Dart code in Markdown files
• Analyze Dart code embedded in Markdown
• Test Dart code embedded in Markdown
• Embedded templates in Markdown
  • Template is commented out
  • Below template, output of template is injected/updated

---

Gabriel Terwesten • GitHub @blaugold • Twitter @GTerwesten • Medium @gabriel.terwesten