Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XDoc Config: create unit test to verify property types and default values #3187

Closed
rnveach opened this issue May 17, 2016 · 7 comments
Closed
Assignees
Milestone

Comments

@rnveach
Copy link
Member

rnveach commented May 17, 2016

For types:

<td><a href="property_types.html#stringSet">list of strings</a></td>

We interchange Type Set and list of types.
<td><a href="property_types.html#boolean">boolean</a></td>

We interchange boolean/Boolean and integer/Integer types.
<td><a href="property_types.html#integer">3</a></td>

We have improper types, 3 instead of Integer.

For default values:


<td><code>empty list</code></td>

We interchange blanks with {}, all files, or empty list for sets depending on the context.
<td><code>{}</code></td>


Some default values are wrong.

There will be 2 hurdles with creating a junit for default values:

  1. Bean fields must have the same name as the setter, which is what BeanUtil sees.
    public void setBaseName(String baseName) {
    baseNamePattern = CommonUtils.createPattern(baseName);
@romani
Copy link
Member

romani commented May 21, 2016

@rnveach ,

please move " We use String in the setter for everything, from regular expressions, file locations, to
custom enumerations." to separate issue, it will not be a just clean up .

@rnveach
Copy link
Member Author

rnveach commented May 22, 2016

I moved it.

rnveach added a commit to rnveach/checkstyle that referenced this issue May 23, 2016
rnveach added a commit to rnveach/checkstyle that referenced this issue May 23, 2016
rnveach added a commit to rnveach/checkstyle that referenced this issue May 23, 2016
rnveach added a commit to rnveach/checkstyle that referenced this issue May 23, 2016
rnveach added a commit to rnveach/checkstyle that referenced this issue May 26, 2016
@romani
Copy link
Member

romani commented May 29, 2016

For types:

is done.

For default values:

is NOT done yet.

rnveach added a commit to rnveach/checkstyle that referenced this issue Jun 5, 2016
rnveach added a commit to rnveach/checkstyle that referenced this issue Jun 5, 2016
rnveach added a commit to rnveach/checkstyle that referenced this issue Jun 5, 2016
rnveach added a commit to rnveach/checkstyle that referenced this issue Jun 5, 2016
rnveach added a commit to rnveach/checkstyle that referenced this issue Jun 6, 2016
@romani
Copy link
Member

romani commented Jun 7, 2016

@rnveach , is smth left as not-fixed here ?

@rnveach
Copy link
Member Author

rnveach commented Jun 7, 2016

@romani Until we align all types in Issue #3212, we can't fully validate strings.
Right now setters are String type, but are then converted to Patterns and custom enumerations. All we see is String right now, so we can't tell the difference to accurately say if it is a String or something else.

These are the current overrides that need to be removed for full validation:


if (clss != String.class && clss != String[].class && result == null) {

@romani
Copy link
Member

romani commented Jun 7, 2016

issue is too big, please split into separate issue (it will be non "miscellaneous" update ) and close this issue.

@rnveach
Copy link
Member Author

rnveach commented Jun 7, 2016

Closed because issue is split

@rnveach rnveach closed this as completed Jun 7, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants