Skip to content

Breaking Changes

Version 1.x

@muhammara/wasm 1.0.0 is the first stable release. The changes below land in a 1.x release because they fix behavior that differed from native Recipe, which Wasm follows (#889, #916).

  • text() without coordinates flows by default. A call without coordinates starts a flow unless it passes flow: false, so the next call without coordinates continues its line. text("a", {}) followed by text("b", {}) drew two lines and now draws ab on one line. The flow is drawn when a call passes flow: false, or when a text() call with coordinates, table(), or endPage() follows. To draw a call right away, pass flow: false:
recipe.text("a", { flow: false }).movedown().text("b", { flow: false });

  • The text cursor stays on the last line of a text box. After a text box, movedown(0, true) reports a position one first-line height above the bottom of the box's last line, without padding or vertical alignment, instead of the position below the box. When the lines share a height, that is the top of the last line. movedown() moves to the line right after the box, so text(), movedown(), text() no longer leaves a blank line between them. Call movedown(2) where the blank line is wanted.

  • A positive Recipe rotation option on text() and the shapes (rectangle(), circle(), polygon(), line(), and the rest) turns content clockwise on the page, the same way as native Recipe and Wasm image(). Before, the same angle turned text and shapes counter-clockwise, so rotated content now leans the other way. Text without rotationOrigin also turns around the x and y given to text(), so a wrapped or aligned text box turns as one block instead of each line around its own baseline start. This corrects a parity bug in a minor release. To keep the earlier direction, negate the angle, for example rotation: -30 instead of rotation: 30. Pass rotationOrigin to turn text around another point. rotateContent() is unchanged and still turns counter-clockwise #916