adfemg
  1. adfemg
  2. ADFEMG-124

[ADFng1-04001] View instance name.

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Won't Fix
    • Labels:
      None

      Description

      I would suggest to apply the convention that View Object instance names must be logical names, often the view's name and don't include any suffix, not the default numerical suffix and also not the ViewObject's suffix 'view'.

      This means that normally my entity and viewobject have the same 'base' name with different suffixes and that they are normally the same as the database table or view and that the logical 'translation' is done the View Object instance as that's the interface to the UI.

        Issue Links

          Activity

          Hide
          Jan Vervecken added a comment -

          related to JIRA issue ADFEMG-94, "[ADFng1-04014] - View object instance names"

          Show
          Jan Vervecken added a comment - related to JIRA issue ADFEMG-94 , " [ADFng1-04014] - View object instance names"
          Hide
          chriscmuir added a comment - - edited

          Splitting this into 2 issues:

          a) VOs having logical names

          The document states a principal of convention over configuration, thus why it doesn't pursue logical names. You're preference is of course valid, and as the document says:

          "Generally the guidelines should be followed but in the cases where it doesn't make sense to do so, where you have your own preference, certainly diverge from the guidelines. However ensure to document why and when this has occurred so your team follows a single guideline rather than an ambiguous set of conflicting guidelines from Oracle and your own efforts."

          b) VO suffixes

          As the document states in the principal section, there is two competing requirements, convention over configuration vs no hungarian notation, with the former taking preference. As the IDE by default creates a suffix View, this is what we leave such that programmer doesn't have to make any unnecessary configurations to the code.

          CM.

          Show
          chriscmuir added a comment - - edited Splitting this into 2 issues: a) VOs having logical names The document states a principal of convention over configuration, thus why it doesn't pursue logical names. You're preference is of course valid, and as the document says: "Generally the guidelines should be followed but in the cases where it doesn't make sense to do so, where you have your own preference, certainly diverge from the guidelines. However ensure to document why and when this has occurred so your team follows a single guideline rather than an ambiguous set of conflicting guidelines from Oracle and your own efforts." b) VO suffixes As the document states in the principal section, there is two competing requirements, convention over configuration vs no hungarian notation, with the former taking preference. As the IDE by default creates a suffix View, this is what we leave such that programmer doesn't have to make any unnecessary configurations to the code. CM.
          Hide
          chriscmuir added a comment -

          No comment back from submitter, issue closed.

          CM.

          Show
          chriscmuir added a comment - No comment back from submitter, issue closed. CM.

            People

            • Assignee:
              Unassigned
              Reporter:
              ainoan
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: