fix: build errors related to project member list

[prateekshourya29]

Description

Type of Change

• Build fix

Summary by CodeRabbit

• Refactor
  • Improved handling of membership join dates to ensure clearer and more consistent display, especially when the join date is unavailable.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The created_at property in the TProjectMembership type was moved from the top-level to within each union member, reflecting its appropriate type per variant. Correspondingly, assignment logic for joining_date in project member details was updated to handle the possible null value of created_at.

Changes

File(s)	Change Summary
packages/types/src/project/projects.d.ts	Relocated created_at from the top-level of TProjectMembership to each union member with variant-specific type.
web/core/store/member/base-project-member.store.ts	Updated assignment of joining_date to use projectMember.created_at ?? undefined for null safety.

Sequence Diagram(s)

sequenceDiagram
    participant Store as base-project-member.store.ts
    participant Types as projects.d.ts

    Store->>Types: Access TProjectMembership
    Note right of Types: created_at is now per union variant
    Store->>Store: Assign joining_date = created_at ?? undefined

Loading

Possibly related PRs

• [WEB-3787] fix: project joining date #7127: Refactors the created_at property in TProjectMembership to be variant-specific and updates its usage in member details, focusing on the same property as this PR.

Suggested labels

ready to merge

Suggested reviewers

• sriramveeraghanta
• gakshita

Poem

A bunny hopped through fields of types,
Moving created_at to where it’s right.
Now each member’s date is crystal clear,
With null or string, it’s tailored here.
Hooray for code that’s neat and bright—
This patch brings data into light! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1608e4f and 212c51d.

📒 Files selected for processing (2)

• packages/types/src/project/projects.d.ts (1 hunks)
• web/core/store/member/base-project-member.store.ts (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.