Uploaded image for project: 'Hybrid Application Console'
  1. Hybrid Application Console
  2. HAC-467

Expand AppInitSDK Use Cases

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • Core

      Once HAC-423 is complete, we'll want to think on is there other ways we can allow Apps to bootstrap the SDK. We want to make sure the path to usage is the least problematic. OpenShift Console & ConsoleDot's HAC -Core are our only use-cases today, but we should be pragmatic about adoption to make the SDK more widely usable.

      Acceptance Criteria

      We should consider more entry points for AppInitSDK

      • Today it serves the "everything from the render flow" in both with or without Redux being used by the app
      • The future we should support the use-cases that want to do some stuff prior to rendering
        • eg. Making initSDK function that can set the variables provided to the AppInitSDK so commonFetch is available in an earlier flow of the App startup (pre-rendering)
        • eg. Making two types of starting components:
          • `InitAppSDKUsingRedux` for when we want to merge with their store (OpenShift Console use-case)
          • `InitAppSDK` would be then the case of "internal store" which we could use ReactContext for (as an example)

              spadgett@redhat.com Samuel Padgett
              aballantyne Andrew Ballantyne
              Archiver:
              rhn-support-sthamilt Stacey Hamilton

                Created:
                Updated:
                Archived: