search

john-kelly / elm-postgrest

Make PostgREST requests in Elm
109 stars 14 forks source link

5.0.0 release #60

Open john-kelly opened 5 years ago

john-kelly commented 5 years ago

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: (https://github.com/john-kelly/elm-postgrest/issues/57)
  2. documentation: (https://github.com/john-kelly/elm-postgrest/issues/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 (https://github.com/john-kelly/elm-postgrest/issues/58)
  2. custom error type (https://github.com/john-kelly/elm-postgrest/issues/59)
  3. composite attributes (https://github.com/john-kelly/elm-postgrest/issues/42)

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

john-kelly commented 5 years ago

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:

Misc:

kfk commented 5 years ago

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.

russelldavies commented 5 years ago

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

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

and copy in the PostgRest.elm file into it.

john-kelly commented 5 years ago

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 😢

kfk commented 5 years ago

Thanks for the support guys. I'd like to test this for building something along the lines of: https://github.com/benoror/ember-postgrest-dynamic-ui

No problem about the release time, I'll need some time also to study this, thanks again for putting this together.

On Mon, Mar 11, 2019 at 8:07 PM John Kelly notifications@github.com wrote:

Thanks for jumping in here @russelldavies https://github.com/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 😢

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/john-kelly/elm-postgrest/issues/60#issuecomment-471679191, or mute the thread https://github.com/notifications/unsubscribe-auth/AA5Pwp2YVVqdMp5bj-VN01msFnaXS4QOks5vVqmAgaJpZM4VtNd0 .

-- Regards,

Alessio Civitillo alessiocivitillo@gmail.com Linkedin: http://it.linkedin.com/in/alessiocivitillo