Snowfakery

Latest version: v3.6.3

Safety actively analyzes 630217 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 8

2.0

Recipes can now merge in data from Salesforce orgs as
records, IDs or datasets. (395 and 401)

Output streams can now be specified as 3rd party libraries. Any Python class name
can be passed to --output-format as long as it adheres to the OutputStream
protocol as shown in examples/YamlOutputStream.py (351)

Snowfakery is thread-safe/multi-processor-ready and available for parallel usage
in CumulusCI. (CumulusCI Repo)

Snowfakery now supports a --reps option as an easier way to repeat a recipe (416)

Snowfakery now accepts LeadingCaps syntax for all fakers, as well as
underscore_separated and everythinglowercase. (403)

Salesforce.ContentVersion and Salesforce.ProfileId convenience functions were added
(421)

Snowfakery now has voluminous documentation about Fakes in many languages and
locales (409)

1.12

Fix a regression: In some contexts it was impossible to call Faker with either
positional arguments or keyword arguments. It is now possible to call with
keyword arguments again. Positional arguments are still disallowed and older
recipes may need to be updated to use keyword arguments. (388)

e.g. `${{fake.sentence(nb_words=4)}}` instead of `${{fake.sentence(4)}}`

Snowfakery now informs you that it is not possible to use `just_once` in
a nested context. Previously, the results of doing so were unpredictable.
(333)

1.11

Add a simple benchmarking tool available with the command `snowbench`. 346

Update the namespace used for inline fakes to support the same new names as
block-based fakes. (i.e. ${{fake.FirstName}} is the same as fake: FirstName) 357

Fix a bug which caused problems outputting images. 351

1.10

Snowfakery now has some of its own built-in "Fake data types". For example "FirstName"
(instead of first_name) and "Username" (which is like a Salesforce Username).
These new names should be more intuitive for Salesforce users. PR 343

Fake "emails" now use domains based on "example.com" and similar domains specified in
RFC 2606. This ensure that they are never real email addresses. Broader domain
email addressses are still available as described in th documentation. PR 343

Fake names are now case agnostic. FIRSTname, firstNAME, firstname, FIRSTNAME,
etc. are all identical. PR 343

1.9

Snowfakery's APIs have expanded. The changes should be backwards-compatible. 315

Add support for embedding external files (text or base64 binary). 322

Add support specifically for Salesforce ContentVersion. 322

1.8.1

Fixed packaging issue.

Page 4 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.