1
0
mirror of https://github.com/Unleash/unleash.git synced 2024-10-18 20:09:08 +02:00
unleash.unleash/website/docs/reference/sdks/svelte.md
Thomas Heartman d5fbd0b743
refactor: move docs into new structure / fix links for SEO (#2416)
## What

This (admittedly massive) PR updates the "physical" documentation
structure and fixes url inconsistencies and SEO problems reported by
marketing. The main points are:

- remove or move directories : advanced, user_guide, deploy, api
- move the files contained within to the appropriate one of topics,
how-to, tutorials, or reference
- update internal doc links and product links to the content
- create client-side redirects for all the urls that have changed.

A number of the files have been renamed in small ways to better match
their url and to make them easier to find. Additionally, the top-level
api directory has been moved to /reference/api/legacy/unleash (see the
discussion points section for more on this).

## Why

When moving our doc structure to diataxis a while back, we left the
"physical' files lying where they were, because it didn't matter much to
the new structure. However, that did introduce some inconsistencies with
where you place docs and how we organize them.

There's also the discrepancies in whether urls us underscores or hyphens
(which isn't necessarily the same as their file name), which has been
annoying me for a while, but now has also been raised by marketing as an
issue in terms of SEO.

## Discussion points

The old, hand-written API docs have been moved from /api to
/reference/api/legacy/unleash. There _is_ a /reference/api/unleash
directory, but this is being populated by the OpenAPI plugin, and mixing
those could only cause trouble. However, I'm unsure about putting
/legacy/ in the title, because the API isn't legacy, the docs are. Maybe
we could use another path? Like /old-docs/ or something? I'd appreciate
some input on this.
2022-11-22 09:05:30 +00:00

4.4 KiB

title
Svelte Proxy SDK
Svelte Proxy SDK is currently at version 0.0.2 and is experimental.

This library can be used with the Unleash Proxy or with the Unleash front-end API. It is not compatible with the regular Unleash client API.

For more detailed information, check out the Svelte Proxy SDK on GitHub.

Installation

npm install @unleash/proxy-client-svelte

Initialization

Import the provider like this in your entrypoint file (typically index.svelte):

<script lang="ts">
	let FlagProvider;

	onMount(async () => {
		const proxyClientSvelte = await import('@unleash/proxy-client-svelte');
		({ FlagProvider } = proxyClientSvelte);
	});

	const config = {
		url: 'https://HOSTNAME/proxy',
		clientKey: 'PROXYKEY',
		refreshInterval: 15,
		appName: 'your-app-name',
		environment: 'dev'
	};
</script>

<svelte:component this={FlagProvider} {config}>
	<App />
</svelte:component>

Alternatively, you can pass your own client in to the FlagProvider:

<script lang="ts">
	import { UnleashClient } from '@unleash/proxy-client-svelte';

	let FlagProvider;

	onMount(async () => {
		const proxyClientSvelte = await import('@unleash/proxy-client-svelte');
		({ FlagProvider } = proxyClientSvelte);
	});

	const config = {
		url: 'https://HOSTNAME/proxy',
		clientKey: 'PROXYKEY',
		refreshInterval: 15,
		appName: 'your-app-name',
		environment: 'dev'
	};

	const client = new UnleashClient(config);
</script>

<svelte:component this={FlagProvider} unleashClient={client}>
	<App />
</svelte:component>

Deferring client start

By default, the Unleash client will start polling the Proxy for toggles immediately when the FlagProvider component renders. You can delay the polling by:

  • setting the startClient prop to false
  • passing a client instance to the FlagProvider
<svelte:component
  this={FlagProvider}
  unleashClient={client}
  startClient={false}
>
  <App />
</svelte:component>

Deferring the client start gives you more fine-grained control over when to start fetching the feature toggle configuration. This could be handy in cases where you need to get some other context data from the server before fetching toggles, for instance.

To start the client, use the client's start method. The below snippet of pseudocode will defer polling until the end of the asyncProcess function.

<script lang="ts">
	const client = new UnleashClient({
		/* ... */
	});

	onMount(() => {
		const asyncProcess = async () => {
			// do async work ...
			client.start();
		};
		asyncProcess();
	});
</script>

<svelte:component this={FlagProvider} unleashClient={client} startClient={false}>
	<App />
</svelte:component>

Usage

Check feature toggle status

To check if a feature is enabled:

<script lang="ts">
	import { useFlag } from '@unleash/proxy-client-svelte';

	const enabled = useFlag('travel.landing');
</script>

{#if $enabled}
<SomeComponent />
{:else}
<AnotherComponent />
{/if}

Check variants

To check variants:

<script lang="ts">
	import { useVariant } from '@unleash/proxy-client-svelte';

	const variant = useVariant('travel.landing');
</script>

{#if $variant.enabled && $variant.name === 'SomeComponent'}
<SomeComponent />
{:else if $variant.enabled && $variant.name === 'AnotherComponent'}
<AnotherComponent />
{:else}
<DefaultComponent />
{/if}

Defer rendering until flags fetched

useFlagsStatus retrieves the ready state and error events. Follow the following steps in order to delay rendering until the flags have been fetched.

<script lang="ts">
	import { useFlagsStatus } from '@unleash/proxy-client-svelte';
	const { flagsReady, flagsError } = useFlagsStatus();
</script>

{#if !$flagsReady}
<Loading />
{:else}
<MyComponent error={flagsError} />
{/if}

Updating context

Follow the following steps in order to update the unleash context:

<script lang="ts">
	import { useUnleashContext, useFlag } from '@unleash/proxy-client-svelte';

	export let userId: string = undefined;

	const updateContext = useUnleashContext();

	onMount(() => {
		updateContext({ userId });
	});

	$: {
		async function run() {
			await updateContext({ userId });
			console.log('new flags loaded for', userId);
		}
		run();
	}
</script>