phenixcoder / feature-flags-chrome-plugin Goto Github PK

Using this action:

uses: Klemensas/chrome-extension-upload-action@$VERSION
with:
  refresh-token: 'xxxxxxxxxxxxxxxxxxxxxx'
  client-id: 'xxxxxxxxxxxxx'
  client-secret: 'xxxxxxxxxxxx'
  file-name: './extension.zip'
  app-id: 'xzc12xzc21cx23'
  publish: true

The workflow should check some sort of test before build. Upon successful build, creates a new version using semantic-release. If version is bumped, then publishes the extension to chrome web store.

• Test / Validate.
• Version Bump check.
• If version bumped, the push to chrome web store.

When feature flags are initialised, the initialise function should check for existing feature flags and their states and apply saved state on top of passed feature flags.

In case of refresh, the updated feature flags get reset.

Please add a license to make it clear if this can be used by others (companies) or not.

https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository

Currently the data flag storage is mapped using windowId and tabId.

Instead of this it should be based on URL like :

1. hostname for Hostname with port and http scheme
2. hostname+path for path also.

While setup, the app should specify which value should be used to map data.

{
   root: 'hostname',  // or 'hostname+path'
}