splitio / angular-sdk-examples

Angular JS SDK examples

Currently, the project is using Angular 15.2.10.

This project was generated with Angular CLI version 9.0.1 and then updated to the version 15.2.10

The goal of this project is to show one way to set up the Split angular utilities in Angular.

Getting started

Optional: If nvm is locally installed, run nvm i to set the required Node version.

• npm install
• npm install -g @angular/cli
• ng serve will start a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Note: To effectively test the SDK, you need to set the corresponding Browser SDK key. The SDK key is available on your Organization Settings page, on the APIs tab. Remember to choose browser type. In addition to that, you may want to create some feature flags in the admin and then update the list of feature flags defined in the code example.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.

If you need help with Split usage, please reach out to [email protected].

angular-sdk-examples's Issues

handling SDK_READY_TIMED_OUT

the complex example has this bit of code

complex example

    // We won't throw an error here, we'll just return the false for the AppResolver to know it should not render the view.
    // A real use case would be to handle that as a control event.
    //
    // There's an advanced use case where you'll react to timeouts but once the SDK gets ready you'll use it.
    // Just showcasing a way you can handle that, but if you have a specific use case we can have more discussions.
    client.on(client.Event.SDK_READY_TIMED_OUT, () => {
      this._isSdkReady = false;
      resolve(false);
    });

why not reject with an error?
if we are not rejecting, how would a retry strategy work here? or is that unnecessary?

SplitFactory blocking protractor tests

Hey,

Hope all of you are doing great. Me and my team are using SplitIO in our project. Angular 8 created with JHipster, but I don't think it matters. Issue that we are facing is that when splitio service/client is running it is blocking our e2e (protractor) tests to perform any actions, like clicking on the button or navigating on the page.

Specifically invoking this line causes tests to start breaking:

SplitFactory({
      ...config
    });

I am not sure why this would be happening and I would really appreciate any help. If you need more information just let me know.