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

Mui5 react18 rebase #1

Closed
wants to merge 207 commits into from

Conversation

nwalker2398
Copy link

Rebased from ProjectMirador/Mirador mud5-react18 branch, added CI, all tests pass.

morpheus-87 and others added 30 commits August 17, 2023 15:54
…ionalization_errors

add missing german translations
Tests would previously fail if OSD version 2.4.2 was installed.
See  ProjectMirador#3792
Additional context and considerations for prospective contributors, external link updates
…fixes

Fix some styling and console errors on mui5 branch
Run CI tests when making PRs against the mui5 branch
cbeer and others added 26 commits December 19, 2023 15:57
…-up-wrappers

Clean up some unnecessary wrappers and clean up workspace styles
…ector

Fix selector for the manifest description or summary by considering the current language
…ne iiif images

- jest specs for image service identification
- jest specs for resource type filters
- ProjectMirador#3789
- IIIF Auth2 services will be members of a probe service
- ProjectMirador#3789
…3789)

- DRY search routines into functions defined in getServices
- all routines should look for Auth2 types and Auth1 profiles
- include search for uncoducmented Auth1 implementation of explicit probe service
- correct a spec name in accessTokens.test.js
- stop refetching accessTokens if state has an ok true/false attribute
- ProjectMirador#3789
- src/state/sagas/auth.js
- src/state/sagas/iiif.js
- src/state/sagas/windows.js
- src/state/selectors/auth.js
- src/state/selectors/canvases.js
@barmintor
Copy link
Member

Am I correct in understanding that issue-3789_auth2-mui5-react18 was our/my original fork, from upstream before mui5/react18, and that mui5-react18-rebase is a rebase of issue-3789_auth2-mui5-react18 on the upstream react18 branch?

If that is correct, I don't think we want to merge anything back - I think we just want the new branch, right?

If that is correct, I think there's some commits we might want to drop - our goal should be the smallest delta possible, right? - at least 1b41071 looks unnecessary.

@nwalker2398
Copy link
Author

nwalker2398 commented Feb 28, 2024

Am I correct in understanding that issue-3789_auth2-mui5-react18 was our/my original fork, from upstream before mui5/react18, and that mui5-react18-rebase is a rebase of issue-3789_auth2-mui5-react18 on the upstream react18 branch?

If that is correct, I don't think we want to merge anything back - I think we just want the new branch, right?

If that is correct, I think there's some commits we might want to drop - our goal should be the smallest delta possible, right? - at least 1b41071 looks unnecessary.

Yes, this is a rebase of issue-3789_auth2-mui5-react18 on the upstream mui5-react18 branch. It makes sense that these changes aren't meant to be merged back into main—I was unsure where the final destination for these was so I made this PR figuring we could just close it if it's unnecessary.

I'll see where I can pare down unnecessary commits—I haven't rebased much before so this is definitely a learning process for me. After that, does it make more sense to keep this as a new branch or merge it into issue-3789_auth2-mui5-react18?

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.

10 participants