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

exporter mapping dimension options look a little anti-intuitive #3001

Open
nnhjy opened this issue Nov 6, 2024 · 0 comments
Open

exporter mapping dimension options look a little anti-intuitive #3001

nnhjy opened this issue Nov 6, 2024 · 0 comments

Comments

@nnhjy
Copy link
Member

nnhjy commented Nov 6, 2024

In the docs, the entity dimension is said to specify "the maximum number of entity’s dimensions that the mapping is able to handle." It also seems like a filter for entities based on the dimension.

When a user sets it to 0, the preview filters out all 1-dimensional entities. Nice to have.
image

Then the user tries setting the dimension to 1. The preview table shows all multi-dimensional entities but excludes the 1-dimensional ones. (Whoops!) And there is no difference in the preview table as the user increases the dimension number to see what is happening.
image

I suppose it could be more intuitive if the preview table also filters out the entities of dimension no larger than the number put in the entity dimension setting. And 1-dimensional entities should also appear when entity dimension is 1 (before we resolve the ambiguity problem (#2814) from the legacy objective classes).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant