-
Notifications
You must be signed in to change notification settings - Fork 432
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
feat(core): releases history #7973
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
No changes to documentation |
⚡️ Editor Performance ReportUpdated Fri, 13 Dec 2024 10:06:40 GMT
Detailed information🏠 Reference resultThe performance result of
🧪 Experiment resultThe performance result of this branch
📚 Glossary
|
Component Testing Report Updated Dec 13, 2024 10:06 AM (UTC) ❌ Failed Tests (6) -- expand for details
|
packages/sanity/src/core/releases/tool/detail/ReleaseDashboardActivityPanel.tsx
Outdated
Show resolved
Hide resolved
3f749c7
to
0e8b2a9
Compare
832db69
to
d69186f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Super solid work, @pedrobonamin! Appreciate the thorough unit tests inclued as well. Left a few comments, please have a look. No blockers for merge I think :)
packages/sanity/src/core/releases/tool/detail/ReleaseActivityListItem.tsx
Outdated
Show resolved
Hide resolved
packages/sanity/src/core/releases/tool/detail/ReleaseStatusItems.tsx
Outdated
Show resolved
Hide resolved
packages/sanity/src/core/releases/tool/detail/events/getReleaseActivityEvents.ts
Show resolved
Hide resolved
vi.resetAllMocks() | ||
}) | ||
it('should not get the events if release is undefined', () => { | ||
testScheduler.run(({expectObservable, hot}) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, cool – first time I've seen this pattern with hot/cold
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First time using it, it's a very nice way to "mock" the observables and indicate they are "alive" and that we could receive updates from it.
|
||
return fetchLogs({fromTransaction: cachedTransactions[0]?.id, toTransaction: toTransaction}) | ||
.pipe( | ||
expand((response) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, neat! Don't think I've ever had a use for expand
before. Makes the whole "keep fetching until reaching the end" logic look so simple!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've been going deep into rxjs
with this latest changes and I'm really surprised how it makes async functions really easy and declarative. Wish I knew all of this earlier.
Description
implements corel-236
Introduces release events, using the
translog
and therelease-events
api.Why we get events from the translog and the api?
The events API doesn't generate events for the edits that happen in the release metadata, we need to get those from the
translog
. Also, the creation event from the API doesn't contain the metadata information, so we get that from the translog.What to review
Testing
Tests have been added for the new observables and logic.
Notes for release