Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat(committees): refactor members tab with governance fields and enhanced form #342
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
Uh oh!
There was an error while loading. Please reload this page.
feat(committees): refactor members tab with governance fields and enhanced form #342
Changes from 1 commit
914c1fba098020f3b8e0aa9d258d048deff2ec3535File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
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.
Render the rest of the new governance fields in the members table.
The form now captures and submits
appointed_byplus the role/voting date ranges, but this table still only rendersRoleandVoting Status. Those values stay invisible after save, so the governance-column part of this PR is still incomplete.Also applies to: 133-140
🤖 Prompt for AI Agents
Uh oh!
There was an error while loading. Please reload this page.
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.
[Blocking] Template literal in Angular binding — will fail at runtime
[href]="`mailto:${member.email}`"Angular template expressions don't support JavaScript template literals (backtick strings). This will throw a template parse error at runtime.
Fix:
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.
Custom skeleton instead of PrimeNG
<p-skeleton>.Problem: The loading state uses hand-rolled skeleton markup with
animate-pulseandbg-gray-200divs.Why it's a problem: The rest of the codebase (
route-loading.component,metric-card.component) uses<p-skeleton>fromprimeng/skeletonfor loading states. Custom skeletons create visual inconsistency (different animation timing, color, border-radius) and bypass theming provided by PrimeNG.Fix: Replace the custom
animate-pulse/bg-gray-200div block with<p-skeleton>elements matching the table row layout. ImportSkeletonModulefromprimeng/skeletonin the component's imports array.Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.