Optional (int) property by value

Open
#331 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
tooling

Research direction

Start by locating the existing optional property implementation and the property APIs it wraps. Review how integer and double values are represented and loaded, then determine the expected disabled-value behavior and add coverage for the proposed optional numeric properties. The issue names no files or tests, so the repository structure must be explored first.

Written by the indexing model from the issue text.

Description

I've come across a lot of configurations that have optional limits that can be disabled by 0 or -1. This could be represented as a Property<Optional<Integer>> so that the application doesn't need to deal with checking if the property is "disabled".

Would be nice for double, too. Probably not for other types? Esp. considering that for String, the default would just be an empty string. But maybe this can be implemented similar to the existing optional property—it just wraps another property.

Dominant language
Java
Stars
44
Forks
21
Avg merge
2d 2h
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from AuthMe/ConfigMe

All issues in AuthMe/ConfigMe

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.