Uploaded image for project: 'OpenMRS Core'
  1. OpenMRS Core
  2. TRUNK-4932

Deprecate ObsService.getComplexObs

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed
    • Could
    • Resolution: Duplicate
    • None
    • None
    • Data Model
    • Low

    Description

      Issues from TODOs:

      From lines 370-373 of ObsService.java:

      • ComplexData. Otherwise returns a simple Obs. TODO: Possibly remove this method. It is
      • confusing because you may have a complexObs, but not want the complexData attached at the
      • time. Nevertheless, you may think that this method is necessary to use, when you could just
      • call getObs(). This will attach the complexData onto the obs.

      This precedes the public Obs getComplexObs method.

      Gliffy Diagrams

        Attachments

          Issue Links

            duplicates

            Sub-task - The sub-task of the issue TRUNK-4994 Remove TODO comment and deprecate method

            • Could - Issue to be addressed as resources permit.
            • Closed

            Sub-task - The sub-task of the issue TRUNK-6094 COPY: Remove TODO comment and deprecate method

            • Could - Issue to be addressed as resources permit.
            • Needs Assessment

            Sub-task - The sub-task of the issue TRUNK-6115 COPY: Remove TODO comment and deprecate method

            • Could - Issue to be addressed as resources permit.
            • Needs Assessment
            relates to

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. TRUNK-324 Go through the TODO items code and create tickets out of them

            • Should - Issue should be completed for its milestone; however, will not delay the milestone.
            • Ready for Work

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. TRUNK-6087 COPY: Go through the TODO items code and create tickets out of them

            • Should - Issue should be completed for its milestone; however, will not delay the milestone.
            • Needs Assessment

            Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. TRUNK-6108 COPY: Go through the TODO items code and create tickets out of them

            • Should - Issue should be completed for its milestone; however, will not delay the milestone.
            • Needs Assessment

            Activity

              People

                Unassigned Unassigned
                mitchellbot James Mitchell
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: