![]() This started out as a fix for #5753 after I felt the approach in #5760 was not the best way to handle this. The problem lies in the way the cutlist data is added to the pattern by the title plugin. The whole cutlist thing was added by a less experienced contributor, and they were a little too focussed on what they were trying to accomplish, rather than keeping an eye on the big picture. In this case, a bunch of points get added to the part to anchor all of the text for the cutlist. This causes problems when inheriting parts because points are added per material, and now we don't know what materials were used and how to remove these points. I appreciate @woutervdub effort to resolve this in #5760 but as I mentioned above, I don't love the approach. Rather than finding a clever way to remove these points, I am of the opinion that they should never have been added in the first place. Specifically, all we are doing is adding one or more lines of text. The idea that you need multiple points for this is an incorrect assumption, and therein lies the root of this problem. So, this refactor adds support to the title macro for 'notes'. These notes will be added below the title. The cutlist info is now just prepended to the notes. So it stops being something 'special' (which it never should have been) and instead just behaves like other text that is placed on the part by the title macro. The only flanking measure required to make this happen was to add support for nested arrays in handling text. This way, you can pass a nested array to concatenate strings in such a way that each part will still be individually translated. And as all text in FreeSewing, to force a linebreak, you just use "\n" as The Dark Lord intended. |
||
---|---|---|
.. | ||
src | ||
build.mjs | ||
CHANGELOG.md | ||
data.mjs | ||
package.json | ||
README.md |
@freesewing/react-components
React components by/for FreeSewing
What am I looking at? 🤔
This repository is the FreeSewing monorepo holding all FreeSewing's websites, documentation, designs, plugins, and other NPM packages.
This folder holds: @freesewing/react-components
If you're not entirely sure what to do or how to start, type this command:
npm run tips
If you don't want to set up a dev environment, you can run it in your browser:
We recommend that you fork our repository and then put
gitpod.io/#<entire-url-of-your-fork
into a browser to start up a browser-based dev environment of your own.
About FreeSewing 💀
Where the world of makers and developers collide, that's where you'll find FreeSewing.
If you're a maker, checkout freesewing.org where you can generate sewing patterns adapted to your measurements.
If you're a developer, the FreeSewing documentation lives at freesewing.dev. The FreeSewing core library is a batteries-included toolbox for parametric design of sewing patterns. But FreeSewing also provides a range of plugins that further extend the functionality of the platform.
If you have NodeJS installed, you can try it right now by running:
npx create-freesewing-pattern
Getting started guides are available for:
The pattern design tutorial will show you how to create your first parametric design.
Support FreeSewing: Become a patron 🥰
FreeSewing is an open source project maintained by Joost De Cock and financially supported by the FreeSewing patrons.
If you feel FreeSewing is worthwhile, and you can spend a few coins without hardship, then you should join us and become a patron.
Links 👩💻
Official channels
- 💻 Makers website: FreeSewing.org
- 💻 Developers website: FreeSewing.dev
- ✅ Support, Issues & Discussions on GitHub
Social media
- 🐦 Twitter: @freesewing_org
- 📷 Instagram: @freesewing_org
Places the FreeSewing community hangs out
License: MIT 🤓
© Joost De Cock.
See the license file for details.
Where to get help 🤯
For Support, please use the Issues & Discussions on GitHub.