-
-
Notifications
You must be signed in to change notification settings - Fork 308
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
Error on unknown plot attributes #2966
Closed
Closed
Changes from 17 commits
Commits
Show all changes
25 commits
Select commit
Hold shift + click to select a range
e034db2
error on unknown plot attributes
jkrumbiegel 8a28123
add `label`
jkrumbiegel 3f6e4fa
delete `xmin` and `xmax` in hvlines
jkrumbiegel dc26934
disallow figure explicitly to fix tests
jkrumbiegel 74f6332
add `fxaa`
jkrumbiegel 04073e2
add lowclip, highclip, nan_color to Text defaults
jkrumbiegel f0a3dd2
delete more unused attributes from contour
jkrumbiegel b5631da
pop `transformation` from attributes
jkrumbiegel 94f7044
rotation -> rotations
jkrumbiegel 61107b6
add `rasterize`
jkrumbiegel badd777
remove old `alpha` keyword
jkrumbiegel 0da784e
add model to allowlist
jkrumbiegel 67f0503
add direction and remove non barplot attrs for hist
jkrumbiegel 2ad1835
add default title xlabel ylabel to raincloud
jkrumbiegel 87ff15c
add `enable_depth` to `volume`
jkrumbiegel 16af75e
remove incorrect huge plot using nonexistent `dist_between_categories`
jkrumbiegel 7626e59
add `absorption` to `volume`
jkrumbiegel de46dd4
add barplot keys to hist
jkrumbiegel c62bd9d
fix waterfall color and bar attrs
jkrumbiegel 78583a5
fix hvspan keys
jkrumbiegel e023aac
add `matcap` to `Mesh`
jkrumbiegel 59680f4
correct arg order in ablines theme
jkrumbiegel 7de4d4b
correct `StepHist` attrs
jkrumbiegel 79bff1a
`ScatterLines` `space`
jkrumbiegel f87e68e
Merge branch 'master' into jk/error-on-unknown-attributes
SimonDanisch File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
inspectable
,material
,texture
,transformation
, are also things which should be added, plus all the GLMakie lighting stuff (specular, diffuse, etc)It would also be nice to have a signature which does not perform this check, for easy programmatic passing of attributes inherited from the parent plot!
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.
transformation
is already removed elsewhere prior to this checkWouldn't it be better to group all backend related keywords under one umbrella rather than just letting them potentially collide with the rest?
I think I would like it better if an RPRMakie plot had
meshscatter(data; RPRMakie = (; material = ...)
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.
same for GLMakie
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.
and
rasterize
in CairoMakieThere 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.
If we want both name checking and the ability to add arbitrary attributes to a plot we need to separate them somehow. I was thinking we could have one whitelisted attribute Dict of core attributes, which may become fields of specific plot object (
struct Scatter ... end
etc) if we want that, and one Dict with everything else.Having
RPRMakie = (; ...)
etc is similar to that I guess. Though I would say attributes that influence other objects (inspectable, label, ...) and overwrites (model, view, ...) should also move out of the directly defined attributes. I guess the latter could also be part of the backend groups. The former is kind of the "random stuff that you want to attach to a plot" group, which I think is useful to have in a dynamic way.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.
You could still do that by doing
plotobject.attributes[:something] = xyz
no? For me it's currently most important to make our user interface more robust against user errorThere 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.
we could also add a
misc
allowed key or something which should only ever be set to anAttributes
instance with further keys. Then we could disallow such a key for any other recipe so we know it will never conflict, and people can use it to carry arbitrary stuff forward. I want to avoid a situation where people make recipes and we break them by introducing some new add-on keyword arg.