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

update prod! #1727

Merged
merged 21 commits into from
Feb 4, 2022
Merged

update prod! #1727

merged 21 commits into from
Feb 4, 2022

Conversation

scottjehl
Copy link
Contributor

No description provided.

jefflembeck and others added 21 commits February 1, 2022 07:56
feat(Request): Add CPClient setting
NOTE: THERE ARE PLANS TO ADD BACK TESTS THAT ARE USER-SCOPED LEVEL OF
PRIVATE

Currently, WPT has two privacy settings: private and public. Public
tests once showed up on the Test History page where _anybody_ could see
them. That was fun, but it's no longer the case for us.

So, now every test we run is private.

BUT, there's a caveat to that. Our version of private just means "we
don't list the URL anymore." It does not gate test results on their user
capabilities.

This is misleading. So, since there is no difference in how we treat
public vs private tests, I'm getting rid of the concept of private tests
until we hook up tests that are actually within the authorized visibility
set of the user.
* feat(Catchpoint Auth): Adding login/logout via CP

This is a big commit.

- Moved www/models to www/src, we will be following this format in the
  future for new files
- Added linting/formating for anything within www/src (PSR12)
- Added a Util class to start migrating things out of common_lib for
  easier testing/referencing
- Add logging in, logging out (and the routes behind this*)

* THIS REQUIRES AN NGINX RESTART

* fixup! feat(Catchpoint Auth): Adding login/logout via CP
chore(format): remove carriage returns
This ensures a profile can be used if it's pages that don't have the simpleadvanced fields.
Add lighthouse to primary results nav
Get rid of the type for now, we need to have a mixed type in there,
because default response can be whatever we want, but that's php 8
fix(Util): Type Error when null passed
Variables getting clobbered in php is a whole thing so this happened and
took out our results page
Updating our AZDO sync action with the new board
fix(RequestContext): s/$request/$request_context
@jefflembeck jefflembeck merged commit 96cbcc6 into prod Feb 4, 2022
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

Successfully merging this pull request may close these issues.

None yet

3 participants