Details

    • Type: Incident report
    • Status: Closed
    • Priority: Critical
    • Resolution: Won't fix
    • Affects Version/s: 2.1.3
    • Fix Version/s: None
    • Component/s: API (A), Frontend (F)
    • Labels:

      Description

      There are a lot of problems with the current node implementation in the frontend and API. Here's a couple of examples:

      1. In get methods "nodeids" default to either the node selected in the dropdown, or the ones checked in the node tree. But the information about the selected nodes is stored in the profiles, which cannot be accessed via the API.
      2. There is no way to specify to create methods on which nodes the objects must be created.
      3. There are a lot of validation bugs caused by incorrect node usage, for instance, when an object is created on one node, but the validation is done on the other.

      Node filtering is a purely frontend-specific feature, and the API should always receive the required node IDs as parameters, not take them from the database.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                jelisejev Pavels Jelisejevs (Inactive)
              • Votes:
                1 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: