You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@
10
10
-[Open a pull request](#open-a-pull-request)
11
11
-[Submit your PR & get it reviewed](#submit-your-pr--get-it-reviewed)
12
12
-[Your PR is merged](#your-pr-is-merged)
13
-
-[Keep contributing as you use MicroStrategy Docs](#keep-contributing-as-you-use-microstrategy-docs)
13
+
-[Keep contributing as you use Strategy Docs](#keep-contributing-as-you-use-strategy-docs)
14
14
15
15
## Getting started
16
16
@@ -21,7 +21,7 @@ Before you begin:
21
21
22
22
### Use the 'Edit' button
23
23
24
-
Navigating a new codebase can be challenging, so we're making that a little easier. As you're using this MicroStrategy Embedding SDK Docs, you may come across an article that you want to make an update to. You can find and click the **Edit** button on the top right corner on that article, which will take you to the file in this repo where you'll make your changes.
24
+
Navigating a new codebase can be challenging, so we're making that a little easier. As you're using this Strategy Embedding SDK Docs, you may come across an article that you want to make an update to. You can find and click the **Edit** button on the top right corner on that article, which will take you to the file in this repo where you'll make your changes.
25
25
26
26
Before you make your changes, check to see if an [issue exists](https://github.com/MicroStrategy/embedding-sdk-docs/issues) already for the change you want to make.
27
27
@@ -44,7 +44,7 @@ Fork using GitHub Desktop:
44
44
45
45
### Make your update
46
46
47
-
Make your changes to the file(s) you'd like to update. Here are some tips and tricks for [using the docs codebase](#working-in-the-microstrategyembedding-sdk-docs-repository).
47
+
Make your changes to the file(s) you'd like to update. Here are some tips and tricks for [using the docs codebase](#working-in-the-strategyembedding-sdk-docs-repository).
48
48
49
49
- Are you making changes to the application code? You'll need **Node.js v16** to run the site locally. See [contributing/development.md](contributing/development.md).
50
50
- Are you contributing to markdown? We use [Markdown](https://www.markdownguide.org/basic-syntax/).
@@ -60,13 +60,13 @@ When you're done making changes and you'd like to propose them for review, use t
60
60
61
61
### Your PR is merged
62
62
63
-
Congratulations! The whole MicroStrategy community thanks you. :sparkles:
63
+
Congratulations! The whole Strategy community thanks you. :sparkles:
64
64
65
65
Once your PR is merged, you will be proudly listed as a contributor in the [contributor chart](https://github.com/MicroStrategy/embedding-sdk-docs/graphs/contributors) and at the bottom of the page you contributed to.
66
66
67
-
### Keep contributing as you use MicroStrategy Docs
67
+
### Keep contributing as you use Strategy Docs
68
68
69
-
Now that you're a part of the MicroStrategy Docs community, you can keep participating in many ways.
69
+
Now that you're a part of the Strategy Docs community, you can keep participating in many ways.
70
70
71
71
**Learn more about contributing:**
72
72
@@ -77,7 +77,7 @@ Now that you're a part of the MicroStrategy Docs community, you can keep partici
-[Starting with an issue](#starting-with-an-issue)
79
79
-[Opening a pull request](#opening-a-pull-request)
80
-
-[Working in the MicroStrategy/embedding-sdk-docs repository](#working-in-the-microstrategyembedding-sdk-docs-repository)
80
+
-[Working in the Strategy/embedding-sdk-docs repository](#working-in-the-strategyembedding-sdk-docs-repository)
81
81
-[Reviewing](#reviewing)
82
82
-[Self review](#self-review)
83
83
-[Test it locally](#test-it-locally)
@@ -87,7 +87,7 @@ Now that you're a part of the MicroStrategy Docs community, you can keep partici
87
87
88
88
## :memo: Types of contributions
89
89
90
-
You can contribute to the MicroStrategy Embedding SDK Docs content and site in several ways. This repo is a place to discuss and collaborate on MicroStrategy Embedding SDK Docs! Our small, but mighty :muscle: docs team is maintaining this repo, to preserve our bandwidth, off topic conversations will be closed.
90
+
You can contribute to the Strategy Embedding SDK Docs content and site in several ways. This repo is a place to discuss and collaborate on Strategy Embedding SDK Docs! Our small, but mighty :muscle: docs team is maintaining this repo, to preserve our bandwidth, off topic conversations will be closed.
91
91
92
92
### :beetle: Issues
93
93
@@ -101,7 +101,7 @@ When we merge those changes, they should be deployed to the live site within 24
101
101
102
102
### :question: Support
103
103
104
-
We are a small team working hard to keep up with the documentation demands of a continuously changing product. Unfortunately, we just can't help with support questions in this repository. If you are experiencing a problem with MicroStrategy, unrelated to our documentation, please [contact MicroStrategy Support directly](https://www.microstrategy.com/support). Any issues, or pull requests opened here requesting support will be given information about how to contact MicroStrategy Support, then closed and locked.
104
+
We are a small team working hard to keep up with the documentation demands of a continuously changing product. Unfortunately, we just can't help with support questions in this repository. If you are experiencing a problem with Strategy, unrelated to our documentation, please [contact Strategy Support directly](https://www.microstrategy.com/support). Any issues, or pull requests opened here requesting support will be given information about how to contact Strategy Support, then closed and locked.
105
105
106
106
### :earth_asia: Translations
107
107
@@ -117,16 +117,16 @@ You can browse existing issues to find something that needs help!
117
117
118
118
You can use the GitHub user interface :pencil2: for some small changes, like fixing a typo or updating a readme. You can also fork the repo and then clone it locally, to view changes and run your tests on your machine.
119
119
120
-
## Working in the MicroStrategy/embedding-sdk-docs repository
120
+
## Working in the Strategy/embedding-sdk-docs repository
121
121
122
122
Here's some information that might be helpful while working on a Docs PR:
123
123
124
124
-[Development](contributing/development.md) - This short guide describes how to get this app running on your local machine.
125
-
-[Content style guide for MicroStrategy Docs](contributing/content-style-guide.md) - This guide covers information about how we style our content and images. It also links to the resources we use for general style guidelines.
125
+
-[Content style guide for Strategy Docs](contributing/content-style-guide.md) - This guide covers information about how we style our content and images. It also links to the resources we use for general style guidelines.
126
126
127
127
## Reviewing
128
128
129
-
We (usually the docs team, but sometimes MicroStrategy product managers, engineers, or supportocats too!) review every single PR. The purpose of reviews is to create the best content we can for people who use MicroStrategy.
129
+
We (usually the docs team, but sometimes Strategy product managers, engineers, or supportocats too!) review every single PR. The purpose of reviews is to create the best content we can for people who use Strategy.
130
130
131
131
:yellow_heart: Reviews are always respectful, acknowledging that everyone did the best possible job with the knowledge they had at the time.
Copy file name to clipboardExpand all lines: contributing/content-style-guide.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -138,7 +138,7 @@ The list below shows the usage of emojis in our Docs site:
138
138
139
139
- Titles, sidebar labels, and headers
140
140
141
-
- These should use **sentence case**. For example, prefer "This is the title from MicroStrategy" over "This Is The Title From MicroStrategy".
141
+
- These should use **sentence case**. For example, prefer "This is the title from Strategy" over "This Is The Title From Strategy".
142
142
- `sidebar_label` should only be used if you want a different title in the sidebar than the `title` in front matter. (Note: For folders, `label` in sidebars.js takes priority over `sidebar_label`)
Copy file name to clipboardExpand all lines: docs/add-functionality/add-event.md
+39-2Lines changed: 39 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ Once you have used the `dossier.create(props)` method to embed a dashboard into
15
15
16
16
## Events
17
17
18
-
Each supported event is described in the table below. You get the EventType from `microstrategy.dossier.EventType`.
18
+
Each supported event is described in the table below. You get the EventType from `microstrategy.dossier.EventType` or `microstrategy.embeddingContexts.EventType`.
Copy file name to clipboardExpand all lines: docs/add-functionality/add-functionality.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,11 +43,11 @@ Once you have embedded a dashboard, you can use helper methods in the Embedding
43
43
44
44
:::tip
45
45
46
-
If you plan to use Embedding SDK on a web page on a different domain from your MicroStrategy environment, please also meet the following requirements. More information in
46
+
If you plan to use Embedding SDK on a web page on a different domain from your Strategy environment, please also meet the following requirements. More information in
Copy file name to clipboardExpand all lines: docs/add-functionality/authoring-library.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Author an embedded dashboard
3
3
description: To allow users to conveniently edit a dashboard, Embedding SDK allows embedding a dashboard in the authoring mode, whether it is during the initial load or in the view mode of the dashboard.
4
4
---
5
5
6
-
Embedding MicroStrategy content within critical business applications empowers users to make smarter decisions by taking advantage of the dashboard development efforts that occur behind the scenes. To allow users to conveniently edit a dashboard, Embedding SDK allows embedding a dashboard in the authoring mode, whether it is during the initial load or in the view mode of the dashboard.
6
+
Embedding Strategy content within critical business applications empowers users to make smarter decisions by taking advantage of the dashboard development efforts that occur behind the scenes. To allow users to conveniently edit a dashboard, Embedding SDK allows embedding a dashboard in the authoring mode, whether it is during the initial load or in the view mode of the dashboard.
Copy file name to clipboardExpand all lines: docs/add-functionality/error-handling.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,15 @@
1
1
---
2
2
title: Error handling
3
-
description: MicroStrategy provides custom error handling in two stages, during dashboard creation and after dashboard creation.
3
+
description: Strategy provides custom error handling in two stages, during dashboard creation and after dashboard creation.
4
4
---
5
5
6
6
By default, Library displays a pop-up dialog when an error occurs, such as when a dataset is not found.
7
7
8
8

9
9
10
-
MicroStrategy provides custom error handling for these kinds of pop-up errors in two stages.
10
+
Strategy provides custom error handling for these kinds of pop-up errors in two stages.
11
11
12
-
MicroStrategy also provides session error handling for session errors in two stages. Because the handling method of the session error is different from other errors, we don't use the custom error handling in this case.
12
+
Strategy also provides session error handling for session errors in two stages. Because the handling method of the session error is different from other errors, we don't use the custom error handling in this case.
13
13
14
14
## Custom error handling
15
15
@@ -67,11 +67,11 @@ microstrategy.dossier
67
67
});
68
68
```
69
69
70
-
### The overall MicroStrategy Library error behavior in embed case
70
+
### The overall Library error behavior in embed case
71
71
72
72
The error generated by the embedded Library or dashboard page would output an error log in the browser console. Besides that,
73
73
74
-
- If `disableCustomErrorHandlerOnCreate` is set to `true` in `microstrategy.dossier.create` or `microstrategy.embeddingContexts.embedLibraryPage`, the custom error handler couldn't be registered. The error would only be shown by a popup error dialog, which is the same as the OOTB MicroStrategy Library behavior;
74
+
- If `disableCustomErrorHandlerOnCreate` is set to `true` in `microstrategy.dossier.create` or `microstrategy.embeddingContexts.embedLibraryPage`, the custom error handler couldn't be registered. The error would only be shown by a popup error dialog, which is the same as the OOTB Library behavior;
75
75
- If `disableCustomErrorHandlerOnCreate` is not set or is `false`:
76
76
- If a custom error handler is set by `errorHandler` or `addCustomErrorHandler(customErrorHandler, false)`, the error would only invoke the custom error handler and wouldn't popup a Library error dialog.
77
77
- If a custom error handler is set by `addCustomErrorHandler(customErrorHandler, true)`, the error would first popup an error dialog, and when the user clicks the button on the error dialog, the custom error handler would be invoked.
@@ -82,7 +82,7 @@ The error generated by the embedded Library or dashboard page would output an er
82
82
When the session expiration error occurs:
83
83
84
84
- If there is no `sessionErrorHandler` defined, the page will show the Library's logout page.
85
-
- If you define a `sessionErrorHandler`, the function will be executed. After 1 minute, the page will forcefully redirect to the OOTB MicroStrategy Library login page.
85
+
- If you define a `sessionErrorHandler`, the function will be executed. After 1 minute, the page will forcefully redirect to the OOTB Library login page.
0 commit comments