inconsistent/undocumented field naming scheme

XMLWordPrintable

    • Type: Incident report
    • Resolution: Won't fix
    • Priority: Minor
    • None
    • Affects Version/s: None
    • Component/s: Frontend (F)

      for example, item for field "store value" has id/name "delta" in directly attached item, but becomes "delta_name" in a templated item.
      while this might be because the field is not editable anymore, the same principle is not applied to all fields - for example, "name" field doesn't have it's id/name changed.

      this sometimes breaks automated tests, so it should be figured out why is it done this way and documented in the guidelines

            Assignee:
            Unassigned
            Reporter:
            richlv
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: