default transformations on 0.9
See original GitHub issuethis lib is mutating my options object with a bunch of defaults. particularly annoying is this:
transformations: {
crop:{},
circle: true,
rotate: true,
}
which leaves my uploads all failing. please do not MUTATE my options object at the very least, and fix this. it even overrides if i put transformations: {}
. garbage
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Transformations in Zeppelin Visualization
Overview · 1. PassthroughTransformation · 2. ColumnselectorTransformation · 3. PivotTransformation · 4. AdvancedTransformation. Spec; Spec: axis; Spec: sharedAxis ...
Read more >torchvision.transforms - PyTorch
Since v0.8.0 all random transformations are using torch default random generator to sample random parameters. It is a backward compatibility breaking change ...
Read more >Transformation — Open3D 0.9.0 documentation
The geometry types of Open3D have a number of transformation methods. In this tutorial we show how to use translate , rotate ,...
Read more >Lesson 9: Data Transformations - STAT ONLINE
The default logarithmic transformation merely involves taking the natural logarithm — denoted l n or l o g e or simply l o...
Read more >Cinder 0.9 Transition Guide
The vectors default construct to zero, and the matrix and quaternion variants default construct to the identity transformation.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Arguments passed to
client.pick
should no longer be mutated in 0.9.1. Thanks again for reporting this.Fair enough.
While I did not write the pick config parser, I now realize to what extent we are mutating the options passed to pick. And it extends beyond
transformations
. This will most certainly be changed before 1.0. Thank you for bringing this up, and for the record I share the opinion that this argument mutation is heinous, whether or not it causes bugs.