Skip to content
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

Create profile pages #976

Closed
thewilkybarkid opened this issue May 30, 2023 · 0 comments
Closed

Create profile pages #976

thewilkybarkid opened this issue May 30, 2023 · 0 comments

Comments

@thewilkybarkid
Copy link
Member

No description provided.

thewilkybarkid added a commit that referenced this issue May 30, 2023
It's a bit hidden in the Zenodo docs, but it's possible to sort by publication date rather than creation date.

Refs #976, https://help.zenodo.org/guides/search/
thewilkybarkid added a commit that referenced this issue May 30, 2023
thewilkybarkid added a commit that referenced this issue May 30, 2023
This change is a prerequisite to removing the hard-coded data.

Refs #976
thewilkybarkid added a commit that referenced this issue May 30, 2023
thewilkybarkid added a commit that referenced this issue May 30, 2023
thewilkybarkid added a commit that referenced this issue May 30, 2023
This change is a prerequisite to removing the ORCID iD hard coding from the route. Note that it doesn't yet load remote data.

Refs #976
thewilkybarkid added a commit that referenced this issue May 30, 2023
erkannt added a commit that referenced this issue May 31, 2023
thewilkybarkid added a commit that referenced this issue May 31, 2023
thewilkybarkid added a commit that referenced this issue May 31, 2023
erkannt added a commit that referenced this issue May 31, 2023
The fetch-mock library turn 0 status codes into 200s.

Refs: #976, 7f65c76
erkannt added a commit that referenced this issue May 31, 2023
This assumes the response has both a given and a family name and that
the given name should precede the family name.

Refs: #976
erkannt added a commit that referenced this issue May 31, 2023
erkannt added a commit that referenced this issue May 31, 2023
thewilkybarkid added a commit that referenced this issue May 31, 2023
thewilkybarkid added a commit that referenced this issue May 31, 2023
thewilkybarkid added a commit that referenced this issue May 31, 2023
thewilkybarkid added a commit that referenced this issue May 31, 2023
thewilkybarkid added a commit that referenced this issue May 31, 2023
thewilkybarkid added a commit that referenced this issue May 31, 2023
thewilkybarkid added a commit that referenced this issue May 31, 2023
thewilkybarkid added a commit that referenced this issue Jun 1, 2023
… step inside the Playwright container

I've tried running the whole job in the Playwright container previously but had trouble enabling Git LFS. I've just discovered that you can run an individual step inside a container. This change allows us to build the app outside of Docker (and so can benefit from things like npm caching, multistage builds etc.). This change worked locally with Act.

Refs #976, 7d29c5f, microsoft/playwright#23388 (comment), https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-using-a-docker-public-registry-action
thewilkybarkid added a commit that referenced this issue Jun 1, 2023
thewilkybarkid added a commit that referenced this issue Jun 1, 2023
thewilkybarkid added a commit that referenced this issue Jun 1, 2023
thewilkybarkid added a commit that referenced this issue Jun 1, 2023
thewilkybarkid added a commit that referenced this issue Jun 1, 2023
thewilkybarkid added a commit that referenced this issue Jun 2, 2023
thewilkybarkid added a commit that referenced this issue Jun 2, 2023
thewilkybarkid added a commit that referenced this issue Jun 2, 2023
This change runs more shards, which are now noticeably quicker to start.

Refs #976, 5e2bf81, dc04b4f
thewilkybarkid added a commit that referenced this issue Jun 2, 2023
Due to the property tests, Jest takes a little while to run. This change splits it into multiple jobs, similar to the integration tests.

Refs #976, https://jestjs.io/docs/next/cli#--shard
thewilkybarkid added a commit that referenced this issue Jun 2, 2023
thewilkybarkid added a commit that referenced this issue Jun 2, 2023
thewilkybarkid added a commit that referenced this issue Jun 2, 2023
thewilkybarkid added a commit that referenced this issue Jun 2, 2023
thewilkybarkid added a commit that referenced this issue Jun 2, 2023
thewilkybarkid added a commit that referenced this issue Jun 2, 2023
thewilkybarkid added a commit that referenced this issue Jun 2, 2023
thewilkybarkid added a commit that referenced this issue Jun 2, 2023
thewilkybarkid added a commit that referenced this issue Jun 2, 2023
Unfortunately, the ORCID API returns strict caching headers that prevent our local cache from working. This commit will be helpful if they decide to relax it.

Refs #976
thewilkybarkid added a commit that referenced this issue Jun 2, 2023
thewilkybarkid added a commit that referenced this issue Jun 5, 2023
thewilkybarkid added a commit that referenced this issue Jun 15, 2023
thewilkybarkid added a commit that referenced this issue Jun 15, 2023
This change uses fetch-mock's 'done' inspection to ensure that it matches the requests as expected to avoid tests passing for the wrong reason (i.e. we didn't mock a response).

I think I've found a bug in fetch-mock where it doesn't recognise that it matched a request when testing a query string independently of the URL. It works as expected when only partially matching the URL.

Refs #976, 047d979, https://www.wheresrhys.co.uk/fetch-mock/#api-inspectiondone, wheresrhys/fetch-mock#657
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant