Add fieldError to export list

[brandon-leapyear]

✨ This is an old work account. Please reference @brandonchinn178 for all future communication ✨

---

Allows people implementing PersistEntity manually to use the fieldError helper

Before submitting your PR, check that you've:

• Bumped the version number
• Documented new APIs with Haddock markup
• Added @since declarations to the Haddock

After submitting your PR:

• Update the Changelog.md file with a link to your PR
• Check that CI passes (or if it fails, for reasons unrelated to your change, like CI timeouts)

[parsonsmatt]

Try merging master - there's an upper bound in place to prevent the cabal solver from picking that version.

[brandon-leapyear]

✨ This is an old work account. Please reference @brandonchinn178 for all future communication ✨

---

What version bound are you referring to?

[parsonsmatt]

persistent-mongoDB needs a < 2.6 constraint on mongoDB package. It's in master, and I was able to get it working by just restarting the CI against master.

[brandon-leapyear]

✨ This is an old work account. Please reference @brandonchinn178 for all future communication ✨

---

This PR is not about persistent-mongodb?

[parsonsmatt]

I know. We didn't have an upper bound on persistent-mongoDB so the cabal builders were failing because they were getting the newest version which was incompatible. That's been fixed. So all we need to get this merged is the checkboxes to be done 😄

[brandon-leapyear]

✨ This is an old work account. Please reference @brandonchinn178 for all future communication ✨

---

ah ok. I was confused because it looks like CI is passing on this branch.

I wasn't sure which of the checkboxes you needed me to fix. Does this change really require a version bump?

[parsonsmatt]

The changelog needs to be updated. If you don't want this released, then you can put it in an Unreleased section instead of a minor version bump. If you do want it to be released soon, then we do need to have a new version number to publish it on Hackage.

A @since annotation on the function denoting the version it was released would also be good.

[brandon-leapyear]

✨ This is an old work account. Please reference @brandonchinn178 for all future communication ✨

---

I wasn't sure what version to put in @since because I'm not setting a next version, so I put @since 2.8.1 for now. Let me know if that needs to be changed

[parsonsmatt]

Released in persistent-template-2.8.2, thanks so much! 😄