Skip to content

Releases: icgc-argo/workflow-ui

3.3.1

22 Jan 19:13
2187df0
Compare
Choose a tag to compare

!!! Breaking Changes !!!

  • This version (and on) of workflow-ui is only compatible with:
    • workflow-management:2.11.0
    • workflow-search:2.6.0

Changelog (3.1.0 → 3.3.1)

  • Change start workflow from REST to GraphQL
  • Update cancelRun to use GraphQL mutation instead of REST API call
  • UI fixes for the New Run Form Modal
  • Add auth header to service-info request in Footer
  • RDPC Region Changes
    • Swap order to be RDPC <region> instead of <region> RDPC
    • Use RDPC region from env var instead of hardcoding on Login page
  • update query to match new SearchResult model
  • Add promise-queue dependency
    • Add promise-queue library for queueing up refresh token requests (as seen in platform-ui)
  • Implement Refresh Token
    • Add global for REFRESH_TOKEN_ENDPOINT
    • Add refreshToken method to Auth context
  • Refresh token on expired/invalid tokens when accessing protected routes
    • Attempt to refresh token if invalid when accessing protected routes
    • Redirects to Login if refresh fails
    • Also fix bug where NavBar would not update on Logout
  • Bug fixes related to Refresh Token
    • Add check for refresh token upon token expiry when changing routes
    • Fix bug where user would get redirected to Login before refresh token fetch was complete
    • Add fetchWithEgoToken HOF for fetch, which automatically grabs the refresh token if current token is invalid
    • Swap regular fetch calls which require auth with fetchWithEgoToken
    • Fix bug NavBar would still show user's details after logging out
  • Fix bug preventing error modals from showing when encountering certain responses from the gateway

3.1.0

03 Dec 19:29
01c806f
Compare
Choose a tag to compare
Merge pull request #89 from icgc-argo/rc/3.1.0

🔖 3.1.0

2.1.1

03 Jul 13:38
b798e10
Compare
Choose a tag to compare
  • Using the new GraphQL api for all search related queries
  • Removed placeholder mutation in favour of straight REST call for workflow init