-
Notifications
You must be signed in to change notification settings - Fork 47
Dev/nivalterman/CV api 5.12.0 #94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1029,6 +1029,14 @@ declare module powerbi { | |
| export interface FilterTypeDescriptor { | ||
| selfFilter?: boolean; | ||
| } | ||
|
|
||
| export const enum PendingChangesType { | ||
| "Filters", | ||
| } | ||
|
|
||
| export type PendingChanges = { | ||
| [key in PendingChangesType]?: boolean; | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think, as we are working with Enum, Now the code above will create the following type structure: "0" is a result of In other words, it would be better to call it something like: |
||
| }; | ||
| } | ||
|
|
||
|
|
||
|
|
@@ -1845,16 +1853,17 @@ declare module powerbi.extensibility.visual { | |
| } | ||
|
|
||
| export interface VisualUpdateOptions extends extensibility.VisualUpdateOptions { | ||
| viewport: IViewport; | ||
| dataViews: DataView[]; | ||
| type: VisualUpdateType; | ||
| viewMode?: ViewMode; | ||
| editMode?: EditMode; | ||
| operationKind?: VisualDataChangeOperationKind; | ||
| jsonFilters?: IFilter[]; | ||
| isInFocus?: boolean; | ||
| subSelections?: powerbi.visuals.CustomVisualSubSelection[]; | ||
| formatMode?: boolean; | ||
| viewport: IViewport; | ||
| dataViews: DataView[]; | ||
| type: VisualUpdateType; | ||
| viewMode?: ViewMode; | ||
| editMode?: EditMode; | ||
| operationKind?: VisualDataChangeOperationKind; | ||
| jsonFilters?: IFilter[]; | ||
| isInFocus?: boolean; | ||
| subSelections?: powerbi.visuals.CustomVisualSubSelection[]; | ||
| formatMode?: boolean; | ||
| pendingChanges?: PendingChanges; | ||
| } | ||
|
|
||
| export interface VisualConstructorOptions extends extensibility.VisualConstructorOptions { | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer to receive some human meaningful value instead of type number. That could help a lot when debugging a visual.

Also, for this type, a single count naming or continuous action is better in my opinion.
Filter = "FILTER"orFiltering = "FILTERING"(uppercase is up to you). While "Filters" might be considered as some set of multiple values.