Skip to content

Commit a4c7783

Browse files
authored
Merge pull request #45 from launchdarkly/emberstevens/ch115846/url-audit-for-sdk-related-repos
Updates outdated Docs site URLs
2 parents a81c168 + 5c40456 commit a4c7783

File tree

3 files changed

+32
-32
lines changed

3 files changed

+32
-32
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44

55
## LaunchDarkly overview
66

7-
[LaunchDarkly](https://www.launchdarkly.com) is a feature management platform that serves over 100 billion feature flags daily to help teams build better software, faster. [Get started](https://docs.launchdarkly.com/docs/getting-started) using LaunchDarkly today!
7+
[LaunchDarkly](https://www.launchdarkly.com) is a feature management platform that serves over 100 billion feature flags daily to help teams build better software, faster. [Get started](https://docs.launchdarkly.com/home/getting-started) using LaunchDarkly today!
88

99
[![Twitter Follow](https://img.shields.io/twitter/follow/launchdarkly.svg?style=social&label=Follow&maxAge=2592000)](https://twitter.com/intent/follow?screen_name=launchdarkly)
1010

@@ -27,7 +27,7 @@ We encourage pull requests and other contributions from the community. Check out
2727
* Gradually roll out a feature to an increasing percentage of users, and track the effect that the feature has on key metrics (for instance, how likely is a user to complete a purchase if they have feature A versus feature B?).
2828
* Turn off a feature that you realize is causing performance problems in production, without needing to re-deploy, or even restart the application with a changed configuration file.
2929
* Grant access to certain features based on user attributes, like payment plan (eg: users on the ‘gold’ plan get access to more features than users in the ‘silver’ plan). Disable parts of your application to facilitate maintenance, without taking everything offline.
30-
* LaunchDarkly provides feature flag SDKs for a wide variety of languages and technologies. Check out [our documentation](https://docs.launchdarkly.com/docs) for a complete list.
30+
* LaunchDarkly provides feature flag SDKs for a wide variety of languages and technologies. Check out [our documentation](https://docs.launchdarkly.com/sdk) for a complete list.
3131
* Explore LaunchDarkly
3232
* [launchdarkly.com](https://www.launchdarkly.com/ "LaunchDarkly Main Website") for more information
3333
* [docs.launchdarkly.com](https://docs.launchdarkly.com/ "LaunchDarkly Documentation") for our documentation and SDK reference guides

src/messages.js

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ export const clientInitialized = function() {
1515
};
1616

1717
const docLink =
18-
' Please see https://docs.launchdarkly.com/docs/js-sdk-reference#initializing-the-client for instructions on SDK initialization.';
18+
' Please see https://docs.launchdarkly.com/sdk/client-side/javascript#initializing-the-client for instructions on SDK initialization.';
1919

2020
export const clientNotReady = function() {
2121
return 'LaunchDarkly client is not ready';
@@ -26,7 +26,7 @@ export const eventCapacityExceeded = function() {
2626
};
2727

2828
export const eventWithoutUser = function() {
29-
return 'Be sure to call `identify` in the LaunchDarkly client: https://docs.launchdarkly.com/docs/js-sdk-reference#section-analytics-events';
29+
return 'Be sure to call `identify` in the LaunchDarkly client: https://docs.launchdarkly.com/sdk/features/identify#javascript';
3030
};
3131

3232
export const invalidContentType = function(contentType) {

typings.d.ts

Lines changed: 28 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ declare module 'launchdarkly-js-sdk-common' {
8080
* immediately after calling `initialize()` (normally they would not be available until the
8181
* client signals that it is ready).
8282
*
83-
* For more information, see the [SDK Reference Guide](https://docs.launchdarkly.com/docs/js-sdk-reference#section-bootstrapping).
83+
* For more information, see the [SDK Reference Guide](https://docs.launchdarkly.com/sdk/features/bootstrapping#javascript).
8484
*/
8585
bootstrap?: 'localStorage' | LDFlagSet;
8686

@@ -153,7 +153,7 @@ declare module 'launchdarkly-js-sdk-common' {
153153
* Whether to send analytics events back to LaunchDarkly. By default, this is true.
154154
*/
155155
sendEvents?: boolean;
156-
156+
157157
/**
158158
* Whether all user attributes (except the user key) should be marked as private, and
159159
* not sent to LaunchDarkly in analytics events.
@@ -195,14 +195,14 @@ declare module 'launchdarkly-js-sdk-common' {
195195

196196
/**
197197
* The capacity of the analytics events queue.
198-
*
198+
*
199199
* The client buffers up to this many events in memory before flushing. If the capacity is exceeded
200200
* before the queue is flushed, events will be discarded. Increasing the capacity means that events
201201
* are less likely to be discarded, at the cost of consuming more memory. Note that in regular usage
202202
* flag evaluations do not produce individual events, only summary counts, so you only need a large
203203
* capacity if you are generating a large number of click, pageview, or identify events (or if you
204204
* are using the event debugger).
205-
*
205+
*
206206
* The default value is 100.
207207
*/
208208
eventCapacity?: number;
@@ -236,18 +236,18 @@ declare module 'launchdarkly-js-sdk-common' {
236236

237237
/**
238238
* Set to true to opt out of sending diagnostics data.
239-
*
239+
*
240240
* Unless `diagnosticOptOut` is set to true, the client will send some diagnostics data to the LaunchDarkly
241241
* servers in order to assist in the development of future SDK improvements. These diagnostics consist of
242242
* an initial payload containing some details of SDK in use, the SDK's configuration, and the platform the
243243
* SDK is being run on, as well as payloads sent periodically with information on irregular occurrences such
244244
* as dropped events.
245245
*/
246246
diagnosticOptOut?: boolean;
247-
247+
248248
/**
249249
* The interval at which periodic diagnostic data is sent, in milliseconds.
250-
*
250+
*
251251
* The default is 900000 (every 15 minutes) and the minimum value is 6000. See [[diagnosticOptOut]]
252252
* for more information on the diagnostics data being sent.
253253
*/
@@ -271,7 +271,7 @@ declare module 'launchdarkly-js-sdk-common' {
271271
/**
272272
* Whether to disable the automatic sending of an alias event when [[identify]] is
273273
* called with a non-anonymous user when the previous user is anonymous.
274-
*
274+
*
275275
* The default value is `false`.
276276
*/
277277
autoAliasingOptOut?: boolean;
@@ -295,7 +295,7 @@ declare module 'launchdarkly-js-sdk-common' {
295295

296296
/**
297297
* An optional secondary key for a user. This affects
298-
* [feature flag targeting](https://docs.launchdarkly.com/docs/targeting-users#section-targeting-rules-based-on-user-attributes)
298+
* [feature flag targeting](https://docs.launchdarkly.com/home/flags/targeting-users#targeting-rules-based-on-user-attributes)
299299
* as follows: if you have chosen to bucket users by a specific attribute, the secondary key (if set)
300300
* is used to further distinguish between users who are otherwise identical according to that attribute.
301301
*/
@@ -365,9 +365,9 @@ declare module 'launchdarkly-js-sdk-common' {
365365
/**
366366
* Describes the reason that a flag evaluation produced a particular value. This is
367367
* part of the [[LDEvaluationDetail]] object returned by [[LDClient.variationDetail]].
368-
*
369-
* This type is separate from `[[LDEvaluationReason]]` for backwards compatibility. In
370-
* earlier versions of this SDK, `[[LDEvaluationReason]]` was incorrectly defined as
368+
*
369+
* This type is separate from `[[LDEvaluationReason]]` for backwards compatibility. In
370+
* earlier versions of this SDK, `[[LDEvaluationReason]]` was incorrectly defined as
371371
* being non-nullable.
372372
*/
373373
interface NonNullableLDEvaluationReason {
@@ -409,7 +409,7 @@ declare module 'launchdarkly-js-sdk-common' {
409409
/**
410410
* Describes the reason that a flag evaluation produced a particular value. This is
411411
* part of the [[LDEvaluationDetail]] object returned by [[LDClient.variationDetail]].
412-
*
412+
*
413413
* Will be null when `[[LDOptions.evaluationReasons]]` is `false`.
414414
*/
415415
export type LDEvaluationReason = NonNullableLDEvaluationReason | null;
@@ -420,7 +420,7 @@ declare module 'launchdarkly-js-sdk-common' {
420420
*
421421
* This is the result of calling [[LDClient.variationDetail]].
422422
*
423-
* For more information, see the [SDK reference guide](https://docs.launchdarkly.com/docs/evaluation-reasons).
423+
* For more information, see the [SDK reference guide](https://docs.launchdarkly.com/sdk/features/evaluation-reasons#javascript).
424424
*/
425425
export interface LDEvaluationDetail {
426426
/**
@@ -445,7 +445,7 @@ declare module 'launchdarkly-js-sdk-common' {
445445
* The basic interface for the LaunchDarkly client. The browser SDK and the Electron SDK both
446446
* use this, but may add some methods of their own.
447447
*
448-
* @see http://docs.launchdarkly.com/docs/js-sdk-reference
448+
* @see https://docs.launchdarkly.com/sdk/client-side/javascript
449449
*
450450
* @ignore (don't need to show this separately in TypeDoc output; all methods will be shown in LDClient)
451451
*/
@@ -470,10 +470,10 @@ declare module 'launchdarkly-js-sdk-common' {
470470
*
471471
* If you want to distinguish between these success and failure conditions, use
472472
* [[waitForInitialization]] instead.
473-
*
473+
*
474474
* If you prefer to use event listeners ([[on]]) rather than Promises, you can listen on the
475475
* client for a `"ready"` event, which will be fired in either case.
476-
*
476+
*
477477
* @returns
478478
* A Promise that will be resolved once the client is no longer trying to initialize.
479479
*/
@@ -498,7 +498,7 @@ declare module 'launchdarkly-js-sdk-common' {
498498
* await client.waitForInitialization();
499499
* doSomethingWithSuccessfullyInitializedClient();
500500
* } catch (err) {
501-
* doSomethingForFailedStartup(err);
501+
* doSomethingForFailedStartup(err);
502502
* }
503503
* ```
504504
*
@@ -509,7 +509,7 @@ declare module 'launchdarkly-js-sdk-common' {
509509
*
510510
* Note that you can also use event listeners ([[on]]) for the same purpose: the event `"initialized"`
511511
* indicates success, and `"failed"` indicates failure.
512-
*
512+
*
513513
* @returns
514514
* A Promise that will be resolved if the client initializes successfully, or rejected if it
515515
* fails.
@@ -530,7 +530,7 @@ declare module 'launchdarkly-js-sdk-common' {
530530
* @param user
531531
* The user properties. Must contain at least the `key` property.
532532
* @param hash
533-
* The signed user key if you are using [Secure Mode](http://docs.launchdarkly.com/docs/js-sdk-reference#secure-mode).
533+
* The signed user key if you are using [Secure Mode](https://docs.launchdarkly.com/sdk/features/secure-mode#configuring-secure-mode-in-the-javascript-client-side-sdk).
534534
* @param onDone
535535
* A function which will be called as soon as the flag values for the new user are available,
536536
* with two parameters: an error value (if any), and an [[LDFlagSet]] containing the new values
@@ -593,7 +593,7 @@ declare module 'launchdarkly-js-sdk-common' {
593593
* The `reason` property of the result will also be included in analytics events, if you are
594594
* capturing detailed event data for this flag.
595595
*
596-
* For more information, see the [SDK reference guide](https://docs.launchdarkly.com/docs/evaluation-reasons).
596+
* For more information, see the [SDK reference guide](https://docs.launchdarkly.com/sdk/features/evaluation-reasons#javascript).
597597
*
598598
* @param key
599599
* The unique key of the feature flag.
@@ -688,16 +688,16 @@ declare module 'launchdarkly-js-sdk-common' {
688688
track(key: string, data?: any, metricValue?: number): void;
689689

690690
/**
691-
* Associates two users for analytics purposes.
692-
*
693-
* This can be helpful in the situation where a person is represented by multiple
694-
* LaunchDarkly users. This may happen, for example, when a person initially logs into
691+
* Associates two users for analytics purposes.
692+
*
693+
* This can be helpful in the situation where a person is represented by multiple
694+
* LaunchDarkly users. This may happen, for example, when a person initially logs into
695695
* an application-- the person might be represented by an anonymous user prior to logging
696696
* in and a different user after logging in, as denoted by a different user key.
697-
*
698-
* @param user
697+
*
698+
* @param user
699699
* The newly identified user.
700-
* @param previousUser
700+
* @param previousUser
701701
* The previously identified user.
702702
*/
703703
alias(user: LDUser, previousUser: LDUser): void;

0 commit comments

Comments
 (0)