feat: deprecate flagd-web provider

[toddbaert]

This PR deprecates the flagd-web provider. The OFREP provider provides comparable functionality over HTTP and, is fully supported by flagd.

There's one significant feature we should release in flagd first before we truly have equivalent features: open-feature/flagd#1854

[gemini-code-assist]

Summary of Changes

Hello @toddbaert, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request initiates the deprecation of the flagd-web provider, directing users towards the OFREP provider as its successor. The OFREP provider offers equivalent HTTP-based functionality and is fully supported by flagd, making it the preferred choice. This change streamlines the available providers, although a pending flagd feature is noted as necessary for complete feature parity.

Highlights

• Provider Deprecation: The flagd-web provider has been officially deprecated, with a strong recommendation to migrate to the OFREP provider for comparable functionality and full flagd support.
• Documentation Update: The README.md for the flagd-web provider has been entirely replaced with a deprecation notice, guiding users to the OFREP provider's NPM package and GitHub repository.
• Codebase Annotation: The FlagdWebProvider class in flagd-web-provider.ts has been marked with a @deprecated JSDoc tag, explicitly advising developers to use OFREPWebProvider instead.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request effectively deprecates the flagd-web provider in favor of the OFREP provider. The changes, which include updating the README with a deprecation notice and adding a @deprecated JSDoc tag to the provider class, are well-aligned with this goal. My review includes a suggestion to refine the wording in the README's deprecation notice for improved clarity and conciseness.

[toddbaert]

e2e test is failing due to pre-existing stability issues fixed in a different PR.

[aepfli]

does this mean, we will also slowly remove the shared directory for flagd and integrate all those things back into the direct flagd provider?

[toddbaert]

does this mean, we will also slowly remove the shared directory for flagd and integrate all those things back into the direct flagd provider?

flagd-core is still useful as a separate component - it's used directly in the playground for example and also in some recent experiments by @jonathannorris to use it in CDN edge workers.

[toddbaert]

I think we can't proceed with this for now until we have some enhancements to OFREP (or decide not to enhance it) that better support realtime updates via SSE or equivalent... at the very least, the polling needs to be made more efficient.

cc @beeme1mr @jonathannorris

Related: open-feature/flagd#1858