ADR: Write a custom validation DSL

[stijn-dejongh]

Generate validator code from PlantUML custom theme specification

Context

Most organizations have business-minded individuals or non-software engineers defining the specifications of the software (internal clients, product owners, analysts, managers, end-users).

Problem

Business validation rules are tedious to maintain, as the translation from business specification into executable validation code involves multiple hand-overs and knowledge-extraction events. In the end, there is seldom time to maintain this consistently.

Current "Behaviour Driven Development" approaches lack the direct feedback to the end users, and are rather verbose (cfr. Cucumber, Gherkin, Finesse, JBehave, ...)

Intent

• ’maintainability:‘ significant increase
• ‘adaptability:‘ significant increase

Solution

• Work with file based validation inputs only, to simplify process and allow for extensibility. ( If your data can be written to a file, it can be validated. Covering most of the real-world use cases for backend BDD approaches).
• Use a minimal plantUML based specification
• Write a plantUML to executable code parser

Reasoning

• Out of the box documentation due to PlantUML visualisation
• Out of the box syntax checks due to PlantUML
• Compatibility with most tech stacks
• Specification can be kept, even if validation framework is removed

Considered alternatives

• Write a custom<insert BDD spec> to ModularValidator implementation: rejected due to stack/dependency impact.
• Write a Kotlin based DSL: rejected due to language onboarding requirements.
• Use an existing tool: rejected as that would defeat the purpose of this project.

References

• JBehave
• Finesse
• Cucumber
• Serenity

Example: Potential DSL API

ValidatorFor(".*IDENTIFIABLE_PART_OF_FILE_NAME.*\\.csv") {
   RecordIdentifier('ROW_ID')
   FieldMatches('FIELD_NAME', 'MAY_NOT_BE_EMPTY')
   FieldExists('JOSKE_WAS_HERE')

   ValidationCase("description") {
     RecordExists('12345')
     RecordHasValue('12345', 'FIELD_NAME', 'expectedValue')
   }
}

[stijn-dejongh]

Implementation plan

• must: write plantUML theme to visualize validation requirements
• must parse example spec at runtime to feed the ModularValitaorBuilder
• should: Write code generator so Validators can be generated at build-time to increase performance
• should: Allow for file structure specification
• could: write maven plugin for QOL and reuse
• dream: write pipeline that takes github issue w/ specification (issue template), generates code, and raises PR

Reasoning

• limit scope to csv files for now
• KISS: only support default file structure. validate usefulness first