You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polygene.apache.org by "Niclas Hedhman (JIRA)" <ji...@apache.org> on 2018/04/19 03:52:00 UTC
[jira] [Commented] (POLYGENE-121) Use parameter names to build
better error messages on constraints violations
[ https://issues.apache.org/jira/browse/POLYGENE-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443547#comment-16443547 ]
Niclas Hedhman commented on POLYGENE-121:
-----------------------------------------
Need to figure out how many cases there are, and whether it is all handled by the same piece of code.
# Construction of a Composite - *{color:#14892c}PARAMETER REPORTED{color}*
# {color:#333333}Setting Property to null on Transient{color} - *{color:#14892c}PROPERTY NAME REPORTED{color}*
# Passing null as method argument - *{color:#14892c}PARAMETER REPORTED{color}*
# ??
> Use parameter names to build better error messages on constraints violations
> ----------------------------------------------------------------------------
>
> Key: POLYGENE-121
> URL: https://issues.apache.org/jira/browse/POLYGENE-121
> Project: Polygene
> Issue Type: Improvement
> Reporter: Paul Merlin
> Priority: Major
> Fix For: 3.1.0
>
>
> See https://docs.oracle.com/javase/tutorial/reflect/member/methodparameterreflection.html for details on parameter names reflection.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)