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.

Sign up for GitHub

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

Jump to bottom

ability to specify postgrest version #35

Open
john-kelly opened this issue Feb 27, 2017 · 2 comments
Open

ability to specify postgrest version #35

john-kelly opened this issue Feb 27, 2017 · 2 comments
Labels
discussion

Comments

@john-kelly
Copy link
Owner

No description provided.

@john-kelly john-kelly changed the title ability to specific postgrest version ability to specify postgrest version May 28, 2018
@john-kelly
Copy link
Owner Author

Ideas:

  • module per version PostgRest.V1
  • sync package versions with postgrest versions (does elm package support this? Branching versions?)
  • if possible, specified on toHttpRequest as apart of options

@russelldavies
Copy link

I haven't tested this (since I don't want to pollute the package index) but after taking a quick look it does appear that you can keep publishing older versions as long as the version number in elm-package.json matches some git tag in your GitHub repo. So my vote would be for option two. It's cleaner and more flexible. Option 3 is the least appealing to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@russelldavies @john-kelly