Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Snowfakery 2.5.0 #599

Merged
merged 1 commit into from
Feb 2, 2022
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions HISTORY.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,16 @@ In the beginning, programmers created the databases. Now the databases were form

And so [Salesforce.org](http://salesforce.org/) said “Let there be data,” and there was Snowfakery. And it was good.

## Snowfakery 2.5
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason you're leaving off the .0 here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems to be the pattern I've been using all along.


Snowfakery now ensures that faked firstnames and lastnames are ASCII alphanumeric
before attemptiing to incorporate them into a fake email (#597)

Snowfakery publishes a JSON Schema for IDE usage (#556)

Snowfakery gives a better error message if a CSV datasource has
rows that have more columns than the header row. (#594)

## Snowfakery 2.4

The Salesforce load order now follows the order of
Expand Down
2 changes: 1 addition & 1 deletion snowfakery/version.txt
Original file line number Diff line number Diff line change
@@ -1 +1 @@
2.4.0
2.5.0