Skip to content
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

Get filter box viz working for explore v2 #1360

Merged
merged 1 commit into from
Nov 4, 2016

Conversation

vera-liu
Copy link
Contributor

Done:

  • Added containerId and getFilters

Todo:

  • get filters working in new formdata and control panel

After:
screen shot 2016-10-15 at 7 10 26 pm

@ascott

@mistercrunch
Copy link
Member

We often point Airflow committers to this article bellow. Please take the time to read it as it's nice to have good commit messages (though no need to overdo it!), that makes for easier PR/project management, a good changelog and can even provide context while dealing with merge conflicts.
http://chris.beams.io/posts/git-commit/

@vera-liu vera-liu force-pushed the vliu_filter_viz branch 2 times, most recently from 1ee81d1 to 2899087 Compare October 16, 2016 18:19
@vera-liu vera-liu changed the title Fixed filter box Get filter box viz working for explore v2 Oct 19, 2016
@@ -42,6 +44,16 @@ class ChartContainer extends React.Component {

selector: `#${this.props.sliceContainerId}`,

setFilter: () => {
// set filter according to data in store
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we add git issues so we know we need to add the logic here and for getFilters once the rest of the controls are done?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ascott
Copy link

ascott commented Nov 3, 2016

LGTM

mock slice object in exploreV2

 - filter_box in exploreV2 was broken because containerID and
   getFilter() were not defined in the mock of slice object
@ascott
Copy link

ascott commented Nov 4, 2016

looks like the tests were passing before merging... what do you think happened? should the revert be merged?

@vera-liu
Copy link
Contributor Author

vera-liu commented Nov 4, 2016

Seems that master was broken when I merged

@dpgaspar dpgaspar mentioned this pull request Apr 30, 2020
12 tasks
zhaoyongjie pushed a commit to zhaoyongjie/incubator-superset that referenced this pull request Nov 17, 2021
zhaoyongjie pushed a commit to zhaoyongjie/incubator-superset that referenced this pull request Nov 24, 2021
zhaoyongjie pushed a commit to zhaoyongjie/incubator-superset that referenced this pull request Nov 25, 2021
zhaoyongjie pushed a commit to zhaoyongjie/incubator-superset that referenced this pull request Nov 26, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels 🚢 0.13.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants