-
Notifications
You must be signed in to change notification settings - Fork 56
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Only export types from default variant of library
When we remove the Types namespace in #909, the RealtimePresence class defined in ably.d.ts will clash with the variable of the same name declared in modules.d.ts. Owen indicated that his preference for resolving this issue is to export the common types (i.e. those currently contained in the Types namespace) from only the default variant and not from the modular variant, so that’s what we do here. Users of the modular variant who wish to refer to the common types will need to import them from the default variant. To maintain TypeDoc’s ability to generate hyperlinks from the references which are contained in the modular variant but which refer to the common types (e.g. some @link tags, BaseRest’s inheritance from AbstractRest), we switch to using a single TypeDoc project to generate documentation for both variants. For reasons that I don’t understand, TypeDoc is unable to resolve the aforementioned @link tags unless I explicitly add a module source [1]. I’d have thought that it’d be sufficient to simply `import` the types that these tags refer to, but doing so makes no difference. So, I’ve added these module sources. Unfortunately, IntelliSense in VS Code doesn’t know what to do with these and the link is not clickable. (I also tried experimenting with TSDoc’s syntax for declaration references [2] but it made no difference). I think we’ll have to live with this; luckily there are only a few such tags. [1] https://typedoc.org/guides/declaration-references/#module-source [2] https://tsdoc.org/pages/tags/link/
- Loading branch information
1 parent
312298a
commit c3a2937
Showing
10 changed files
with
60 additions
and
69 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
# Ably JavaScript Client Library SDK API Reference | ||
|
||
The JavaScript Client Library SDK supports a realtime and a REST interface. The JavaScript API references are generated from the [Ably JavaScript Client Library SDK source code](https://github.com/ably/ably-js/) using [TypeDoc](https://typedoc.org) and structured by classes. | ||
|
||
The realtime interface enables a client to maintain a persistent connection to Ably and publish, subscribe and be present on channels. The REST interface is stateless and typically implemented server-side. It is used to make requests such as retrieving statistics, token authentication and publishing to a channel. | ||
|
||
There are two variants of the Ably JavaScript Client Library SDK: | ||
|
||
- [Default variant](modules/ably.html): This variant of the SDK always creates a fully-featured Ably client. | ||
- [Modular (tree-shakable) variant](modules/modules.html): Aimed at those who are concerned about their app’s bundle size, this allows you to create a client which has only the functionality that you choose. | ||
|
||
View the [Ably docs](https://ably.com/docs/) for conceptual information on using Ably, and for API references featuring all languages. The combined [API references](https://ably.com/docs/api/) are organized by features and split between the [realtime](https://ably.com/docs/api/realtime-sdk) and [REST](https://ably.com/docs/api/rest-sdk) interfaces. |
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.