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

Events V2: implement indexing for events #8087

Merged
merged 11 commits into from
Nov 27, 2024
Merged

Events V2: implement indexing for events #8087

merged 11 commits into from
Nov 27, 2024

Conversation

rikukissa
Copy link
Member

No description provided.

@rikukissa rikukissa added the 🚀 Ready to deploy Deployment automation should pick this PR up and start auto-deploying it label Nov 26, 2024
@rikukissa rikukissa requested a review from naftis November 26, 2024 14:14
Copy link

Oops! Looks like you forgot to update the changelog. When updating CHANGELOG.md, please consider the following:

  • Changelog is read by country implementors who might not always be familiar with all technical details of OpenCRVS. Keep language high-level, user friendly and avoid technical references to internals.
  • Answer "What's new?", "Why was the change made?" and "Why should I care?" for each change.
  • If it's a breaking change, include a migration guide answering "What do I need to do to upgrade?".

@@ -62,18 +64,23 @@ export const appRouter = router({
return getEventById(input)
}),
actions: router({
notify: publicProcedure.input(ActionNotifyInput).mutation((options) => {
notify: publicProcedure.input(NotifyActionInput).mutation((options) => {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why don't we need .omit({ type }) here?


import { z } from 'zod'

const Status = z.enum([
Copy link
Collaborator

@naftis naftis Nov 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the actions were defined as a const object, this would align better with Zod so should we use this method there as well. Can the specific statuses be accessed with Status.enum.CREATED or sth?

Comment on lines +72 to +81
id: { type: 'keyword' },
type: { type: 'keyword' },
status: { type: 'keyword' },
createdAt: { type: 'date' },
createdBy: { type: 'keyword' },
createdAtLocation: { type: 'keyword' },
modifiedAt: { type: 'date' },
assignedTo: { type: 'keyword' },
updatedBy: { type: 'keyword' },
data: { type: 'object', enabled: true }
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wonder if this could be satisfies EventDocument'ed in someway

@rikukissa rikukissa enabled auto-merge (squash) November 27, 2024 13:04
@ocrvs-bot
Copy link
Collaborator

Your environment is deployed to https://ocrvs-7875.opencrvs.dev

@naftis naftis self-requested a review November 27, 2024 13:28
Copy link
Collaborator

@naftis naftis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@rikukissa rikukissa merged commit 1f26eed into develop Nov 27, 2024
67 checks passed
@naftis naftis deleted the ocrvs-7875 branch November 27, 2024 13:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🚀 Ready to deploy Deployment automation should pick this PR up and start auto-deploying it
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement indexing events to Elasticsearch using IndexedRecord
3 participants