Skip to content

Evaluate Optional use #351

@Zarquan

Description

@Zarquan

Our use of Optional is inconsistent.
In theory Optional is a nice thing, but it does not work well with generics.
In some cases we return an Optional, in other cases we unwrap the JPA result and just return null.

        if (optional.isPresent())
            {
            return optional.get();
            }
        else {
            return null;
            }

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions