Also, curious your thoughts on this change (not fully tested, but types all work out): https://gist.github.com/patcon/9f5fb664a2359c27b9390bf45d99e7cc

Basically, I was seeing availableRoles passed through levels and being processed in a few places, and it seemed like this was a very hook-able thing. The graphql query should be cached (I recall someone mentioned we already had SWR in our tools?), and so there's no explicit need to be passing the product of the query down through prop layers, since it will only call it once, right? (I understood this to be a benefit of what SWR unlocked -- that the query hook can be called lots of times right from the place where it's needed, and there's no added cost)

Looks good! Though I'd added a new UpdateUserPage.stories.tsx and renamed the old one to UpdateUserForm.stories.tsx, which was actually the extent of the component it rendered (not the Page). This is only worth mentioning because the new UpdateUserPage.stories.tsx was what made these new interface elements visible in storybook, and otherwise they don't have stories, since they're outside the form :)

Add new permissions to team policy methods

Add delete team mutation

Update and add unit tests for policy methods

Updated pool policy for view actions

Merge branch 'main' into feature/5783-update-team-policies

Update test to verify that base_user cannot query any team members

stub out base date input

add initial validation for date

Updated Pool policy for create, update, and publish actions

Updated Pool policy for changing closing dates and deleting

Added field level permissions for pools

backend suspended filter

Fixed broken tests

Merge branch 'main' into feature_5781_update-pool-policies

Fix broken jest test

remove flex properties

move types to own file

allow hiding segments

replace hardcoded labels with messages

Merge branch 'main' into feature/5783-update-team-policies

🛠️ Tooling

This issue is for adding e2e testing support for Safari/Webkit to complement the existing Chrome support.

🕵️ Details

We are currently only running our cypress e2e tests against the Chrome browser. This led to us being caught with a safari bug in prod involving switching languages: https://talent-cloud.slack.com/archives/CB424V61J/p1679435736584859

Cypress now has experimental support for testing against webkit, which is the engine that backs Safari browser: https://www.cypress.io/blog/2022/09/13/cypress-10-8-experimental-run-tests-in-webkit/

Details: https://docs.cypress.io/guides/guides/launching-browsers?ref=cypress.io#WebKit-Experimental

🙋‍♀️ Proposed Solution

We could likely do this in separate workflow runs, perhaps with a GitHub Action workflow matrix, so that it would be about the same run time for e2e tests to run.

✅ Acceptance Criteria

• [ ] CI runs include e2e tests against the WebKit browser.
• [ ] None of the existing e2e tests should fail

🛑 Blockers

None.

FYI someone did this here: https://github.com/felvin-search/gpt-repository-loader :)

Added docs for Cloudflare URLFWD record type to HOWTO.md.

Added SPF anti-spoof for ForwardEmail and Gmail.

Merge pull request #57 from g0v-network/spf-anti-spoof-g0v.london

Add SPF anti-spoof for ForwardEmail and Gmail

For g0v.london domain. Helps prevent our mail from going to spam.

For g0v.london domain. Helps prevent our mail from going to spam.

Fixed bug and ensure root DNS is proxied via cloudflare.

This isn't well-documented, but Cloudflare's provider allow setting up page rules to redirect pages to other domains.

This is helpful because @ronnywang's amazing 301 redirector app (that redirects via TXT records in DNS), throws errors when the origin url is https (which chrome now automatically adds)

Added URLFWD for g0v.london apex domain.

Added lenient flag for g0v.london in order URLFWD to work.

Added a no-op A record. Fixed URLFWD metadata.

Removed leniency flag.

Merge pull request #52 from g0v-network/try-urlfwd-type

Add URLFWD for g0v.london apex domain

Need this to ensure forwardemail keeps working -- which is used to manage email forwarding via this repo. The .london domain as seen as high-risk and need it, which is apparently high-risk to use their service.

Added email verification for forwardemail.

Merge pull request #56 from g0v-network/fix-forwardemail-g0v.london

Add forwardemail verification

Need this to ensure forwardemail keeps working -- which is used to manage email forwarding via this repo. The .london domain as seen as high-risk and need it, which is apparently high-risk to use their service.

Added venues@g0v.london email alias.

Merge pull request #54 from g0v-network/venues-g0v-london-email

Add venues@g0v.london email alias

Upgraded octodns to use extracted providers.

Updated workflow path triggers.

Merge pull request #55 from g0v-network/upgrade-octodns

Upgrade octodns

Added URLFWD for g0v.london apex domain.

Added lenient flag for g0v.london in order URLFWD to work.

Added a no-op A record. Fixed URLFWD metadata.

Removed leniency flag.