-
Notifications
You must be signed in to change notification settings - Fork 627
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
Can't sort by subobject field #3727
Comments
Thank you for the issue report! I'm going to look into it. |
Here is another problematic example to consider. What if we use a field that is not used anywhere else. We need to automatically flatten it. {
"$schema": "https://vega.github.io/schema/vega-lite/v2.4.1.json",
"data": {
"values": [
{"name": "a0", "a": {"i": 0}, "b": 2},
{"name": "a1", "a": {"i": 1}, "b": 3},
{"name": "a2", "a": {"i": 2}, "b": 1}
]
},
"mark": "bar",
"encoding": {
"x": {"field": "b", "type": "quantitative"},
"y": {"field": "name", "type": "ordinal",
"sort": {
"order": "descending",
"op": "sum",
"field": "a.i"
}
}
}
} |
domoritz
added a commit
that referenced
this issue
May 9, 2018
@iliatimofeev Can you check whether #3728 fixes the problem in your larger example? |
domoritz
added a commit
that referenced
this issue
May 10, 2018
domoritz
added a commit
that referenced
this issue
May 10, 2018
This was referenced May 14, 2018
domoritz
added a commit
that referenced
this issue
May 18, 2018
domoritz
added a commit
that referenced
this issue
May 18, 2018
domoritz
added a commit
that referenced
this issue
May 18, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Can't sort by field stored in properties of geojson object.
Vega-light processes fields with dot in name but not in "sort field definition object"
Simplified example to reproduce situation :
this example on bl.ocks.org
The text was updated successfully, but these errors were encountered: