-
Notifications
You must be signed in to change notification settings - Fork 0
Import bulk of code from River UI project #1
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
Conversation
92b0adf to
906b5d3
Compare
|
@bgentry Thoughts? |
Here, move the API framework, which is currently duplicated in two projects, over to its own repository so that we can reuse it between them. It's new home will be `riverapiframe` [1]. [1] riverqueue/apiframe#1
Here, move the API framework, which is currently duplicated in two projects, over to its own repository so that we can reuse it between them. It's new home will be `riverapiframe` [1]. [1] riverqueue/apiframe#1
bgentry
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM aside from possible naming ideas which I dropped in Slack, your call 🚀
apiendpoint/api_endpoint.go
Outdated
| // Package apiendpoint provides a lightweight API framework for use with River | ||
| // UI. It lets API endpoints be defined, then mounted into an http.ServeMux. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can probably drop the river UI reference and generalize this description.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
|
@brandur oh, you probably want to throw an MIT license on this too |
Here, import the framework code from the River UI project at [1]. I've added some READMEs, configuration files, etc., but otherwise very little has changed. There are a couple small things like adding `printf` variants for errors (which we'll need for Go 1.24 because it doesn't let you pass only a message to a printf-like function, and removing errors for specific types like jobs/queues/workflows (those will like in River UI instead). [1] https://github.com/riverqueue/riverui/tree/master/internal
Cool, done. Also renamed the repo to just "apiframe". |
Corrects a few straggling problems with the rename done in #1. CI still passed there, so I thought I'd gotten everything, but didn't.
Corrects a few straggling problems with the rename done in #1. CI still passed there, so I thought I'd gotten everything, but didn't.
Corrects a few straggling problems with the rename done in #1. CI still passed there, so I thought I'd gotten everything, but didn't.
Here, move the API framework, which is currently duplicated in two projects, over to its own repository so that we can reuse it between them. It's new home will be `riverapiframe` [1]. [1] riverqueue/apiframe#1
Here, move the API framework, which is currently duplicated in two projects, over to its own repository so that we can reuse it between them. It's new home will be `riverapiframe` [1]. [1] riverqueue/apiframe#1
Here, import the framework code from the River UI project at [1].
I've added some READMEs, configuration files, etc., but otherwise very
little has changed. There are a couple small things like adding
printfvariants for errors (which we'll need for Go 1.24 because it doesn't let
you pass only a message to a printf-like function, and removing errors
for specific types like jobs/queues/workflows (those will like in River
UI instead).
[1] https://github.com/riverqueue/riverui/tree/master/internal