Giters

john-kelly / elm-postgrest

Make PostgREST requests in Elm

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

5.0.0 release

john-kelly opened this issue · comments

commented

The current plan is to release the next version of the library in sync with the 0.19 release of Elm.

With that being said, there are still a few things I'd like to finish before an official release:

  1. embed alias updates: (#57)
  2. documentation: (#12)
  3. misc api name changes + updates (no issues for that right now)

Additionally, there are a few issue we may want to consider/think about before the next release. At the very least we should examine if they are candidates for non major bump updates:

  1. upsert (#58)
  2. custom error type (#59)
  3. composite attributes (#42)

At the time of writing, my focus is on documentation.

commented

Just wanted to update here re: status of 5.0.0 release. Things are coming along nicely, but I've decided not to rush. If you need this package, please continue to just use a vendored local version -- my apologies if this is an inconvenience to you.

Main:

  • embed alias updates: (#57)
    • i'm starting to work on this one. it's possible we publish without it (as it can very likely be fixed with a patch), however, I think it's doable for this release
  • documentation: (#12)
    • i'm pretty happy with the state of the docs, so I'm going to focus on other things now. these can always be improved with patches.
  • misc api name changes + updates (no issues for that right now)
    • breaking this out into a new issue! (#62)

Misc:

  • upsert (#58)
    • this can be added in minor version bump, so i'm going to postpone
  • custom error type (#59)
    • i'm still thinking about this one a bit and it may make it into this release
  • composite attributes (#42)
    • i have not yet thought about this one in detail, however, i'm going to postpone it. if it's a major bump in future, so be it
commented

Just wondering if you had any updates on the new release? Else, could you give us a quick comment on what is the best way to go with the vendored approach? I was going through the docs on elm-lang and realized some api's were missing like "createOne" so maybe it would be good to also update the official docs on the vendored approach.

commented

I use a vendor directory in my elm.json file:

...
    "source-directories": [
        "src",
        "vendor"
    ],
 ...

and copy in the PostgRest.elm file into it.

commented

Thanks for jumping in here @russelldavies. I suggest this approach as well.

In terms of a general update on the status of the 5.0.0 release, I unfortunately just haven't had the time to work on this. I could probably do a release AS IS to make things a bit easier for people to get started, however, I think it makes sense to move people towards the vendor'd approach so that they can make quick and dirty modifications to the code in the event of a bug.

I have not abandoned this project, however, it's hard to prioritize since my company hasn't yet adopted elm 😢

commented