Skip to content

Commit 3a7627b

Browse files
ali-hamudali-hamud
authored
Merge pull request microsoft#79 from Microsoft/merge-dev-into-master
remove everything related to visuals in dev branch. dev branch with visuals support is backed-up to dev-visuals branch.
2 parents 80ea784 + f45f3dc commit 3a7627b

15 files changed

Lines changed: 20 additions & 965 deletions

‎dist/ifilterable.d.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
import * as models from 'powerbi-models';
33
/**
44
* Decorates embed components that support filters
5-
* Examples include reports, pages and visuals
5+
* Examples include reports and pages
66
*
77
* @export
88
* @interface IFilterable

‎dist/page.d.ts‎

Lines changed: 0 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
/*! powerbi-client v2.1.1 | (c) 2016 Microsoft Corporation MIT */
22
import { IFilterable } from './ifilterable';
33
import { IReportNode } from './report';
4-
import { Visual } from './visual';
54
import * as models from 'powerbi-models';
65
/**
76
* A Page node within a report hierarchy
@@ -59,17 +58,6 @@ export declare class Page implements IPageNode, IFilterable {
5958
* @returns {(Promise<models.IFilter[]>)}
6059
*/
6160
getFilters(): Promise<models.IFilter[]>;
62-
/**
63-
* Gets all the visuals on the page.
64-
*
65-
* ```javascript
66-
* page.getVisuals()
67-
* .then(visuals => { ... });
68-
* ```
69-
*
70-
* @returns {Promise<Visual[]>}
71-
*/
72-
getVisuals(): Promise<Visual[]>;
7361
/**
7462
* Removes all filters from this page of the report.
7563
*
@@ -102,22 +90,4 @@ export declare class Page implements IPageNode, IFilterable {
10290
* @returns {Promise<void>}
10391
*/
10492
setFilters(filters: models.IFilter[]): Promise<void>;
105-
/**
106-
* Creates a Visual object given a name for the visual.
107-
*
108-
* Normally you would get Visual objects by calling `page.getVisuals()` but in the case
109-
* that the visual name is known and you want to perform an action on a visual such as setting a filter
110-
* without having to retrieve it first you can create it directly.
111-
*
112-
* Note: Because you are creating the visual manually there is no guarantee that the visual actually exists in the report and the subsequence requests could fail.
113-
*
114-
* ```javascript
115-
* const visual = report.page('ReportSection1').visual('BarChart1');
116-
* visual.setFilters(filters);
117-
* ```
118-
*
119-
* @param {string} name
120-
* @returns {Visual}
121-
*/
122-
visual(name: string): Visual;
12393
}

‎dist/powerbi.d.ts‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,6 @@ export { Report } from './report';
88
export { Tile } from './tile';
99
export { IEmbedConfiguration, Embed } from './embed';
1010
export { Page } from './page';
11-
export { Visual } from './visual';
1211
declare global {
1312
interface Window {
1413
powerbi: service.Service;

‎dist/powerbi.js‎

Lines changed: 15 additions & 136 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

‎dist/powerbi.js.map‎

Lines changed: 1 addition & 1 deletion
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

0 commit comments

Comments
 (0)