theseems / clinq

Experimental validation mini-framework

Hi there 👋

My name is Alexey Akhundov. I am a student at HSE, Faculty of Computer Science, Software Engineering.

As a software engineer, I specialize in backend technologies.

I like coding, learning and using algorithms, data structures, designing architecture, in general, almost everything related to CS.

Links 🔗

🌐 My Website
📱 Telegram

clinq's Issues

Standalone "Validator" object

Implement a standalone validator in which we can bake ClinQ and then call it on data that needs to be validated.

Spring error collecting support

Implement SpringCheckErros which hooks into spring validator's errors.

Add javadocs for the API

There definitely should be a kind of documentation for the API.
Let's start by adding simple Javadoc to the interfaces.

What to do with optional pipes?

Now it's just impossible to configure optional pipes.
Need to figure out what to do with them.

There are a few possible scenarios:

• Delete them completely (i guess it's just of no frequent use)
• Add support for their configuration.

Make `when` play with a consumer instead of requiring separate checker.

Example:

var checker = Clinq.<Some>checker()
    .when(some -> some.getField() == 2, someOther -> someOther
        .with(other -> other % 2 == 0))

Out-of-place error message and blocking declarations.

It would be cool to have some long error messages separated from the check syntactically

var checker = Clinq.<Some>checker()
    .and(smth)
      .error("oh smth does not work")

with blocking:

var checker = Clinq.<Some>checker()
    .and(smth)
      .error("oh smth does not work and it block everything")
      .blocking()

Add new features examples to README

Need to add examples for:

• Error messages/blocking (in-place)
• Error messages/blocking (out-of-place)