-
Notifications
You must be signed in to change notification settings - Fork 0
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
Move Projects Service into Biblio Backoffice #1380
Comments
To Do
See https://github.ugent.be/Universiteitsbibliotheek/biblio/tree/issue-1380. |
Notes:
P.S. Feel free to move these notes somewhere else. I just need a place to put these |
nics
added a commit
that referenced
this issue
Apr 29, 2024
verheyenkoen
pushed a commit
that referenced
this issue
May 3, 2024
nics
added a commit
that referenced
this issue
May 3, 2024
* Refactored add/suggest publication project popup to templ #1402 * set preferred name frontoffice route (see #1380) * diable feature flags code for now * bump river version * Added URLBuilder for constructing outgoing url's (#1476) * Added URLBuilder for constructing outgoing url's * Renamed constructor and changed base url argument to type *url.URL * Renamed url builder methods: - WithPath -> Path - AddQuery -> AddQueryParam - WithQuery -> Query * Altered Query method to accept both raw queries (string) and bindable structs * remove double div id=modal (#1480) * fix issue 1478 (#1479) * remove unused base handler code; comment unreleased orcid handler; remove deprecated/unused gohtml (#1477) * Removed hard-coded frontend URL #1402 --------- Co-authored-by: nsteenla <[email protected]> Co-authored-by: Nicolas Franck <[email protected]>
🚧 🚧 On hold, see #1595 🚧 🚧 Last commit before revert: https://github.com/ugent-library/biblio-backoffice/tree/people_projects |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Epic
We would like to move the projects service functionality into Biblio Backoffice instead of keeping it a standalone service.
Rationale:
Success criteria
Implementation suggestion
Goal: for now, it's a semi-isolated service within the backoffice monolith.
The text was updated successfully, but these errors were encountered: