docs: add page in useful tips about transform() parameters and options #154
Conversation
* chore: regenerate package-lock and fix related issues * chore: update image-js * chore: update cspell * chore: update node version in CI * chore: update clsx * chore: update and simplify cspell action * chore: update immer * chore: update react-icons * chore: build on cloudflare with node 22 * chore: update react
* chore: update prettier * chore: update eslint * chore: update typescript * chore: regenerate package-lock
* feat: add algolia search * chore: remove unrelated md file * chore: remove orama
I took inspiration from https://docusaurus.io/blog/releases/3.0 for the title and path. Refs: https://docusaurus.io/docs/api/themes/configuration#announcement-bar
- Put system requirements at the top - Change slug to `getting-started` - Change to MDX since it uses React components. - Remove Vite tutorial - Proofread
Re-exported with inkscape as plain SVG and optimized with svgo Closes: #139
…l-tips-about-transform-parameters-and-options
EscapedGibbon
force-pushed
the
125-add-page-in-useful-tips-about-transform-parameters-and-options
branch
from
3fc1c0c to
a13b1c3
Compare
Deploying image-js-docs with
|
| Latest commit: |
4ff2f94
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://c4de99b8.image-js-docs.pages.dev |
| Branch Preview URL: | https://125-add-page-in-useful-tips.image-js-docs.pages.dev |
EscapedGibbon
force-pushed
the
125-add-page-in-useful-tips-about-transform-parameters-and-options
branch
from
d059511 to
a77814a
Compare
EscapedGibbon
force-pushed
the
125-add-page-in-useful-tips-about-transform-parameters-and-options
branch
from
8a78449 to
b48970f
Compare
There was a problem hiding this comment.
Why is the value 255 here and not an array for the RGB value?
Also, can you use another color that does not exist in the image yet, it would make it clearer which pixels are not part of the original image and which are.
Basically, with inverse set to true you kind of "revert" an image back to the states that it was before the matrix transformed.
This sentence is not very clear. I think you can remove it, what you explain before it is already clear.
When true, the function automatically calculates the required output dimensions.
I think you have to remind what happens when false, that is that size of destination = size of source.
There are also some interactions / incompatibilities between width, height and fullImage. I suppose you are not supposed to specify fullImage to true and also width, height together. What happens in that case?
EscapedGibbon
force-pushed
the
125-add-page-in-useful-tips-about-transform-parameters-and-options
branch
from
6cca264 to
83f7514
Compare
It seems the idea was to have a gray background, so one value was enough.
|
EscapedGibbon
deleted the
125-add-page-in-useful-tips-about-transform-parameters-and-options
branch
No description provided.