Uploaded image for project: 'stripes-core'
  1. stripes-core
  2. STCOR-1

Write a section of the Developer's Guide about parent-child component relationships

    XMLWordPrintable

Details

    Description

      This will be mostly based on what we learned disentangling <UserPermissions> from <ViewUser>, as discussed initially in LIBAPP-147, and subsequently in STRIPES-278, STRIPES-279 and STRIPES-280.

      TestRail: Results

        Attachments

          Issue Links

            blocks

            Umbrella - STRIPES-254 Work on the Stripes Module Developer's Guide

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            is blocked by

            Task - A task that needs to be done. STRIPES-279 Pull availablePermissions down into <UserPermissions>

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Task - A task that needs to be done. STRIPES-280 Remove the "viewUserProps" property from <UserPermissions>

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Task - A task that needs to be done. STRIPES-293 Make a proof-of-concept joining component

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Closed
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. LIBAPP-147 Permissions: Can View Permissions Assigned to Users

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Activity

              People

                mike Mike Taylor
                mike Mike Taylor
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Time Tracking

                    Estimated:
                    Original Estimate - 0 minutes
                    0m
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 2 hours
                    2h

                    TestRail: Runs

                      TestRail: Cases