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

Updates the README with descriptions of Orville some sample code #338

Merged
merged 3 commits into from
Oct 27, 2023

Conversation

qxjit
Copy link
Member

@qxjit qxjit commented Oct 27, 2023

This is probably easiest to review by browsing files on the commit to merge here: https://github.com/flipstone/orville/tree/42fb5446cb5dd5f394cac1480b7fcf28642bb7e9

docs/README.md Outdated
## Why Orville?

Orville is not meant to replace existing PostgreSQL libraries in the Haskell
ecosystem, but to complement them. It has the power to satsify most experienced
Copy link
Contributor

Choose a reason for hiding this comment

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

satsify -> satisfy

docs/README.md Outdated
Comment on lines 25 to 26
hand yet doesn't require absolute type-safety between your custom SQL
statements result sets and the Haskell types they decode into, Orville may be
Copy link
Contributor

Choose a reason for hiding this comment

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

Did you mean "your custom SQL statements' result sets" here?

Copy link
Member Author

Choose a reason for hiding this comment

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

Really I think it should be "your customs SQL statements, their result sets and...". Thanks!

docs/README.md Outdated

## Just show me some code!

Ok! Here's a very simple application that inserts to entities of a `Pet` model and finds one of them based on its name.
Copy link
Contributor

Choose a reason for hiding this comment

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

I think the "to" here is unnecessary.

Copy link
Member Author

Choose a reason for hiding this comment

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

You're right. It should probably say "inserts some entities" though rather than just "inserts entities"

Comment on lines +71 to +74
{- |
It's good practice to create newtype specific to each entity to hold its
primary key value
-}
Copy link
Contributor

Choose a reason for hiding this comment

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

newtype -> newtypes; missing period at end of comment.

Comment on lines +102 to +105
{- |
Marshaller above is associated with the @pet@ table. The marshallers fields
will define the column of the table.
-}
Copy link
Contributor

Choose a reason for hiding this comment

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

marshallers -> marshaller's; column -> columns

@qxjit qxjit merged commit c3bdceb into master Oct 27, 2023
@qxjit qxjit deleted the update-readme branch October 27, 2023 18:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants