Memo for self: to remember rejected but potentially useful features.
- "minimal context width"
- Postponed until the final decision about key styling.
- Should it define any node geometry of scalars only? Or scalar strings only?
- Multiline double-quoted and plain scalars support
- Complex keys styling
- TBH, nobody uses that :). All use strings and may sometimes be integers. So, currently all complex keys are forced to flow (just because "nobody cares").
- Need to decide: do we need a more generic API for "styling everything", or stay on scalars (or even scalar strings) only.
- Comments and empty space (basic support)
- ~ same way as Go parser.
- Not sure it's worth diving into CST direction. But possible. Not enough info to decide.
- Optimize dumper style regexps
- Probably, regexps for base chars can be expanded. Right now, nobody cares about dumper speed. And improvement is not guaranteed. Full expansion is not worth the effort - code will become absolutely unmaintainable.
Other
- Recheck presenter data flow
- Probably the content of the context parameter may be reorganized.
- Recheck event parser regexes for spec BNF compliance.
Memo for self: to remember rejected but potentially useful features.
Other