Skip to content

parseErrorHuman on try.purescript.org #217

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Conversation

jamesdbrock
Copy link
Member

For when parseErrorHuman becomes available on try.purescript.org

Checklist:

  • Added the change to the changelog's "Unreleased" section with a link to this PR and your username
  • Linked any existing issues or proposals that this pull request should close
  • Updated or added relevant documentation in the README and/or documentation directory
  • Added a test for the contribution (if applicable)

@JordanMartinez
Copy link
Contributor

If you want to update the package set in Try PureScript, you can read through the Release Guide on that repo. We have to be careful about package set sizes because of the amount of memory we have. However, so far, it hasn't been an issue.

@jamesdbrock
Copy link
Member Author

Thanks @JordanMartinez . parsing is already in the Try PureScript package set, so eventually that package set will include this version of parsing with the new parseErrorHuman function. I’ll just wait until then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy