The data-marketplace from equinor

Todos

Talk with the Raidx team about setup with internal network
Set up application in Radix
Define AD group(s) for application
Create new internal repository for radix config

Acceptance criteria

PR's merged to main are automatically deployed to production environment
Production environment is reachable for people on the internal network
Users need to authenticate to be able to use the app

Get most viewed assets from Collibra API

Create "Request access" step for checkout wizard

Figma sketch

User should not be able to go to the next step before filling out a description.

The description should not exceed a character limit (TBD).

Implement "Add to cart"

When the user clicks the "Add to cart" button on an asset, the assets should be added to the shopping cart.

Acceptanse criteria

It should be possible to add an asset to the cart
The cart must keep track on the number of items added
The cart must know which assets are added
The cart icon in the nav bar must display the correct number if items added (if not empty)

Update authentication implementation

The current implementation doesn't refresh access token when it expires.

In order for the access token to get refreshed, we shouldn't check for whether or not localStorage has an access_token (as seen here).

Additionally we can update the whole auth flow to be more legible and easier to follow.

Essentially, we might be looking at an implementation like this:

Look at this example for ✨inspiration✨

Utilize i18n package for static text

To make static texts easier to maintain, and potential translations down the line easier to implement, we should add a package like next-i18next.

This will allow us to store static text in one place, which will make it easier to maintain copy.

Acceptance criteria

All texts are added to a file for English text
The components use these texts instead of hard coded text inside the code itself

Use real shopping cart data in the Cart view

AB#84045

Discuss the workflow for removing cart items

How should the workflow be if an user want to remove some previously added assets from the cart?

Criteria

It must be possible to remove an item from the shopping cart

AB#78544

Remove potentially unnecessary useEffects()

React 18 somewhat changes the behaviour for useEffects, so we should go through the code base and see if some of the useEffects should have been removed.

https://beta.reactjs.org/learn/you-might-not-need-an-effect

TODO

Identify potential "anti-patterns" with our current useEffects

Acceptance criteria

No superfluous re-renders and/or state evaluations

AB#84039

Add github actions integration checks

Building off from previous projects integration checks.
Nextjs runs eslint as part of its build process, so we won't need a seperate step for that. Test will come in ones we stabilize a little more.

Forward >=400 status codes from Collibra

Communities not displaying on search page

Get Equinor community ID from Collibra

Create "Terms of Use" step for checkout wizard

Figma sketch

The user should not be able to go the next step unless they accept the terms of use.

Add login

The Collibra API has an endpoint that lets us authenticate the user. Authentication is session based, and the endpoint will return a session ID, in addition to some user data.

Checkout: Restore checkout state on refresh

When a user refreshes during the checkout process or navigate back and/or forward in the checkout process, they should automatically get redirected to the step they were on and state should be restored

AB#84042