hhmi merge requestshttps://gitlab.coko.foundation/hhmi/hhmi/-/merge_requests2024-03-04T14:53:51Zhttps://gitlab.coko.foundation/hhmi/hhmi/-/merge_requests/351Draft: Resolve "Report issue with published item"2024-03-04T14:53:51ZGrigor MaloDraft: Resolve "Report issue with published item"Closes #308Closes #308phase 3Grigor MaloGrigor Malohttps://gitlab.coko.foundation/hhmi/hhmi/-/merge_requests/349Coko server upgrade and remove pubsweet dependencies2024-03-21T17:16:04ZGrigor MaloCoko server upgrade and remove pubsweet dependencies* upgrade coko server to 3.10.0
* import pubsweet methods from coko server
* create migrations script and execute during dev server setup* upgrade coko server to 3.10.0
* import pubsweet methods from coko server
* create migrations script and execute during dev server setupGrigor MaloGrigor Malohttps://gitlab.coko.foundation/hhmi/hhmi/-/merge_requests/322Draft: Chat box for chat ui2024-01-08T11:29:36ZMRdevTaggDraft: Chat box for chat uiMRdevTaggMRdevTagghttps://gitlab.coko.foundation/hhmi/hhmi/-/merge_requests/32Suggestion: Question navigation buttons as links2023-03-27T14:14:28ZGrigor MaloSuggestion: Question navigation buttons as linksNoticing that the current implementation of the back button is a bit buggy (assuming Back refers to the dashboard, if you opened the page on a new tab and click Back nothing happens), and in order to have the benefits of using client sid...Noticing that the current implementation of the back button is a bit buggy (assuming Back refers to the dashboard, if you opened the page on a new tab and click Back nothing happens), and in order to have the benefits of using client side rendering and having a real link (that you can open in new tab for example), i propose the following:
- render the buttons as links by providing a valid href attribute (which it receives by props)
- on a normal click, prevent default behavior (which loads the new page), and call the method provided by props to navigate to the new url using client side renderingYannis BarlasYannis Barlas