website content update feedback #2440
Conversation
📝 WalkthroughWalkthroughThe changes involve modifications to multiple components within the application. The Changes
Suggested reviewers
Poem
Tip 🌐 Web search-backed reviews and chat
Warning Review ran into problems🔥 ProblemsErrors were encountered while retrieving linked issues. Errors (1)
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
New Website2 changes available for preview here |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🔭 Outside diff range comments (2)
website2/src/app/clean-air-forum/partners/page.tsx (1)
46-49: Address security concern with dangerouslySetInnerHTML.Similar to the sponsorships page, this usage of dangerouslySetInnerHTML needs sanitization.
+import DOMPurify from 'dompurify'; <div dangerouslySetInnerHTML={{ - __html: renderContent(data.partners_text_section), + __html: DOMPurify.sanitize(renderContent(data.partners_text_section)), }} />🧰 Tools
🪛 Biome (1.9.4)
[error] 46-46: Avoid passing content using the dangerouslySetInnerHTML prop.
Setting content using code can expose users to cross-site scripting (XSS) attacks
(lint/security/noDangerouslySetInnerHtml)
website2/src/app/clean-air-forum/schedule/page.tsx (1)
35-37: Address security concern with dangerouslySetInnerHTML in AccordionItem.The AccordionItem component uses dangerouslySetInnerHTML without sanitization.
+import DOMPurify from 'dompurify'; <div className="text-sm text-gray-600" dangerouslySetInnerHTML={{ - __html: renderContent(subText) + __html: DOMPurify.sanitize(renderContent(subText)) }} />🧰 Tools
🪛 Biome (1.9.4)
[error] 36-36: Avoid passing content using the dangerouslySetInnerHTML prop.
Setting content using code can expose users to cross-site scripting (XSS) attacks
(lint/security/noDangerouslySetInnerHtml)
🧹 Nitpick comments (8)
website2/src/app/clean-air-forum/sponsorships/page.tsx (1)
12-17: Add type safety to partner filtering.The partner filtering logic uses
anytype which reduces type safety. Consider defining an interface for the partner object structure.+interface Partner { + id: number; + category: string; + partner_logo_url: string; +} + - const sponsorPartner = data.partners - ?.filter((partner: any) => partner.category === 'Sponsor Partner') + const sponsorPartner = data.partners + ?.filter((partner: Partner) => partner.category === 'Sponsor Partner')website2/src/app/clean-air-forum/glossary/page.tsx (1)
24-26: Use a slug generation library to handle edge cases.The
createSlugfunction may not cover all special characters or internationalization nuances. Utilizing a library ensures more reliable slug creation.Apply this diff to use
slugify:+import slugify from 'slugify'; ... const createSlug = (title: string) => { - return title.split(',')[0].trim().toLowerCase().replace(/\s+/g, '-'); + return slugify(title.split(',')[0].trim(), { lower: true }); };Install
slugifywith:npm install slugifywebsite2/src/store/index.ts (1)
4-4: Maintain consistent naming conventions for reducers.To keep the codebase consistent, consider renaming
forumtoforumReducer, aligning withmodalReducerandcountryReducer.Apply this diff:
-import forum from './slices/forumSlice'; +import forumReducer from './slices/forumSlice'; ... reducer: { modal: modalReducer, country: countryReducer, - forum: forum, + forum: forumReducer, },Ensure the export in
forumSlice.tsis updated if necessary.Also applies to: 11-11
website2/src/store/slices/forumSlice.ts (1)
12-16: Define a specific type foractiveTabto enhance type safety.Currently,
activeTabis a generalstring, which might lead to invalid values. Defining a union type restricts it to accepted tab names.Apply this diff:
+type ForumTab = 'About' | 'Agenda' | 'Speakers'; // Add other tabs as needed ... interface ForumState { events: ForumEvent[]; selectedEventIndex: number; - activeTab: string; + activeTab: ForumTab; } const initialState: ForumState = { events: [], selectedEventIndex: 0, - activeTab: 'About', + activeTab: 'About', };This ensures
activeTabonly holds valid tab names, improving reliability.Also applies to: 18-22
website2/src/views/Forum/TabNavigation.tsx (2)
13-23: Consider adding type safety to the tabs array.While moving tabs to a separate array improves maintainability, adding a type definition would enhance type safety and documentation.
+type Tab = { + href: string; + text: string; +}; + -const tabs = [ +const tabs: Tab[] = [ { href: '/clean-air-forum', text: 'About' }, // ... rest of the tabs ];
33-46: Consider using href as key instead of index.Using array indices as keys might cause issues with React's reconciliation process if the tabs array order changes.
-{tabs.map((link, index) => ( +{tabs.map((link) => ( <Link - key={index} + key={link.href} href={link.href} // ... rest of the props >website2/src/app/clean-air-forum/layout.tsx (2)
41-61: Extract slug matching logic to a utility function.The slug matching logic is complex and could benefit from being moved to a separate utility function for better maintainability and testability.
+const findEventIndexBySlug = (events: Event[], slug: string): number => { + const normalizedSlug = slug.replace(/-/g, ' ').toLowerCase(); + return events.findIndex((event) => { + const cleanTitle = event.title + .split(',')[0] + .trim() + .toLowerCase() + .replace(/-/g, ' '); + return cleanTitle === normalizedSlug; + }); +}; useEffect(() => { if (slug && events.length > 0) { - const normalizedSlug = slug.replace(/-/g, ' ').toLowerCase(); - const index = events.findIndex((event) => { - const cleanTitle = event.title - .split(',')[0] - .trim() - .toLowerCase() - .replace(/-/g, ' '); - return cleanTitle === normalizedSlug; - }); + const index = findEventIndexBySlug(events, slug); if (index !== -1 && index !== selectedEventIndex) { dispatch(selectEvent(index)); } } }, [slug, events, selectedEventIndex, dispatch]);
69-71: Consider adding a fallback UI instead of returning null.A fallback UI would provide better user experience when no event is selected.
if (!selectedEvent) { - return null; + return ( + <div className="min-h-screen flex items-center justify-center"> + <p className="text-gray-500">No event selected. Please try again later.</p> + </div> + ); }
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (10)
website2/src/app/clean-air-forum/glossary/page.tsx(1 hunks)website2/src/app/clean-air-forum/layout.tsx(1 hunks)website2/src/app/clean-air-forum/partners/page.tsx(2 hunks)website2/src/app/clean-air-forum/schedule/page.tsx(1 hunks)website2/src/app/clean-air-forum/sponsorships/page.tsx(1 hunks)website2/src/store/index.ts(1 hunks)website2/src/store/slices/forumSlice.ts(1 hunks)website2/src/views/Forum/AboutPage.tsx(0 hunks)website2/src/views/Forum/TabNavigation.tsx(1 hunks)website2/src/views/cleanairforum/PaginatedSection.tsx(2 hunks)
💤 Files with no reviewable changes (1)
- website2/src/views/Forum/AboutPage.tsx
🧰 Additional context used
🪛 Biome (1.9.4)
website2/src/app/clean-air-forum/sponsorships/page.tsx
[error] 28-28: Avoid passing content using the dangerouslySetInnerHTML prop.
Setting content using code can expose users to cross-site scripting (XSS) attacks
(lint/security/noDangerouslySetInnerHtml)
website2/src/app/clean-air-forum/glossary/page.tsx
[error] 80-80: Avoid passing content using the dangerouslySetInnerHTML prop.
Setting content using code can expose users to cross-site scripting (XSS) attacks
(lint/security/noDangerouslySetInnerHtml)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: build-push-website2-deploy-preview
🔇 Additional comments (5)
website2/src/views/cleanairforum/PaginatedSection.tsx (1)
15-18: LGTM! Good improvement in type definitions.The updated type definitions for the logos prop provide better type safety and clarity.
website2/src/app/clean-air-forum/partners/page.tsx (1)
60-61: LGTM! Clear and descriptive section titles.The updated titles "Convening partners and Collaborators" and "Funding Partners and Sponsors" better reflect the content organization.
Also applies to: 102-103
website2/src/app/clean-air-forum/schedule/page.tsx (1)
17-24: LGTM! Good error handling in time formatting.The formatTime function includes proper error handling and fallback for invalid time values.
website2/src/views/Forum/TabNavigation.tsx (2)
6-6: Nice type definition!Explicit type definition as
React.FCimproves type safety and code clarity.
25-27: Good UX improvement!The smooth scroll to top after tab navigation enhances user experience.
| dangerouslySetInnerHTML={{ | ||
| __html: renderContent(data.sponsorship_opportunities_partners), | ||
| }} | ||
| /> |
There was a problem hiding this comment.
Address security concern with dangerouslySetInnerHTML.
Using dangerouslySetInnerHTML with user-provided content can expose the application to XSS attacks.
Consider using a secure HTML sanitizer:
+import DOMPurify from 'dompurify';
<div
dangerouslySetInnerHTML={{
- __html: renderContent(data.sponsorship_opportunities_partners),
+ __html: DOMPurify.sanitize(renderContent(data.sponsorship_opportunities_partners)),
}}
/>📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| dangerouslySetInnerHTML={{ | |
| __html: renderContent(data.sponsorship_opportunities_partners), | |
| }} | |
| /> | |
| import DOMPurify from 'dompurify'; | |
| // ... other imports and code | |
| <div | |
| dangerouslySetInnerHTML={{ | |
| __html: DOMPurify.sanitize(renderContent(data.sponsorship_opportunities_partners)), | |
| }} | |
| /> |
🧰 Tools
🪛 Biome (1.9.4)
[error] 28-28: Avoid passing content using the dangerouslySetInnerHTML prop.
Setting content using code can expose users to cross-site scripting (XSS) attacks
(lint/security/noDangerouslySetInnerHtml)
| dangerouslySetInnerHTML={{ | ||
| __html: renderContent(selectedEvent.glossary_details), | ||
| }} | ||
| ></div> |
There was a problem hiding this comment.
Avoid using dangerouslySetInnerHTML to prevent XSS vulnerabilities.
Using dangerouslySetInnerHTML can expose the application to cross-site scripting (XSS) attacks. It's safer to sanitize the HTML content before rendering or avoid using this prop altogether.
Consider sanitizing the content using a library like dompurify:
+import DOMPurify from 'dompurify';
...
<div
className="md:w-2/3 space-y-4"
dangerouslySetInnerHTML={{
- __html: renderContent(selectedEvent.glossary_details),
+ __html: DOMPurify.sanitize(renderContent(selectedEvent.glossary_details)),
}}
></div>Remember to install dompurify:
npm install dompurify🧰 Tools
🪛 Biome (1.9.4)
[error] 80-80: Avoid passing content using the dangerouslySetInnerHTML prop.
Setting content using code can expose users to cross-site scripting (XSS) attacks
(lint/security/noDangerouslySetInnerHtml)
| // Fetch forum events from the API. | ||
| const { data: forumEvents, isLoading } = useForumEvents(); | ||
| const dispatch = useDispatch(); | ||
| const searchParams = useSearchParams(); | ||
|
|
||
| // When events are fetched, update the Redux slice. | ||
| useEffect(() => { | ||
| if (forumEvents && forumEvents.length > 0) { | ||
| dispatch(setEvents(forumEvents)); | ||
| } | ||
| }, [forumEvents, dispatch]); |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Add error handling for API failures.
While the Redux integration is clean, the code should handle potential API failures gracefully.
const { data: forumEvents, isLoading } = useForumEvents();
+const { data: forumEvents, isLoading, error } = useForumEvents();
const dispatch = useDispatch();
useEffect(() => {
+ if (error) {
+ // Handle error appropriately
+ console.error('Failed to fetch forum events:', error);
+ return;
+ }
if (forumEvents && forumEvents.length > 0) {
dispatch(setEvents(forumEvents));
}
-}, [forumEvents, dispatch]);
+}, [forumEvents, error, dispatch]);Committable suggestion skipped: line range outside the PR's diff.
|
New Website2 changes available for preview here |
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (2)
website2/src/app/clean-air-forum/partners/page.tsx (2)
32-38: Consider adding proper TypeScript interfaces for partner objects.The implementation is good, but using
anytype reduces type safety. Consider defining a proper interface for partner objects to improve maintainability and catch potential issues at compile time.+interface Partner { + id: string; + category: string; + partner_logo_url: string; +} + +interface PartnerLogo { + id: string; + logoUrl: string; +} - const programPartners = data.partners - ?.filter((partner: any) => partner.category === 'Program Partner') - .map((partner: any) => ({ + const programPartners = data.partners + ?.filter((partner: Partner) => partner.category === 'Program Partner') + .map((partner: Partner): PartnerLogo => ({
102-102: Remove empty comment.The empty comment on line 102 should be removed or replaced with meaningful content.
- {/* */}
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
website2/src/app/clean-air-forum/partners/page.tsx(4 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: build-push-website2-deploy-preview
🔇 Additional comments (2)
website2/src/app/clean-air-forum/partners/page.tsx (2)
68-68: Header updates look good!The updated section headers maintain consistent formatting while better reflecting the partner categories.
Also applies to: 131-131
103-121: Program Partners section implementation looks good!The section follows the established pattern and maintains consistency with other partner sections.
|
New Website2 changes available for preview here |
There was a problem hiding this comment.
Actionable comments posted: 2
🔭 Outside diff range comments (1)
website2/src/app/clean-air-forum/program-committee/page.tsx (1)
15-24: Add type definitions for committee members.Replace
anytype with proper interfaces to improve type safety.+interface Person { + id: string; + category: string; +} const committeeMembers = useMemo( () => data?.persons?.filter( - (person: any) => + (person: Person) => person.category === 'Committee Member' || person.category === 'Committee Member and Key Note Speaker' || person.category === 'Speaker and Committee Member', ), [data?.persons], );
🧹 Nitpick comments (6)
website2/src/app/clean-air-forum/logistics/page.tsx (1)
10-10: Add type safety for the data object.Consider adding proper type definitions for the data object returned by
useForumData()to improve type safety and maintainability.- const data = useForumData(); + interface ForumData { + travel_logistics_vaccination_details: string; + travel_logistics_visa_details: string; + } + const data = useForumData() as ForumData;website2/src/app/clean-air-forum/glossary/page.tsx (1)
25-27: Extract slug creation logic to a utility function.Consider moving the slug creation logic to a separate utility file for reusability and testing.
// utils/stringUtils.ts +export const createSlug = (title: string): string => { + return title.split(',')[0].trim().toLowerCase().replace(/\s+/g, '-'); +}; // page.tsx - const createSlug = (title: string) => { - return title.split(',')[0].trim().toLowerCase().replace(/\s+/g, '-'); - }; +import { createSlug } from '@/utils/stringUtils';website2/src/app/clean-air-forum/schedule/page.tsx (1)
3-3: Consider extracting HTML sanitization logic into a utility function.The DOMPurify sanitization is repeated in multiple places. Let's create a reusable utility function to reduce code duplication.
+// In utils/sanitizeUtils.ts +import DOMPurify from 'dompurify'; +import { renderContent } from './quillUtils'; + +export const sanitizeContent = (content: string) => { + return DOMPurify.sanitize(renderContent(content)); +}; -__html: DOMPurify.sanitize(renderContent(data?.schedule_details)), +__html: sanitizeContent(data?.schedule_details), -__html: DOMPurify.sanitize( - renderContent(data?.registration_details), -), +__html: sanitizeContent(data?.registration_details),Also applies to: 91-91, 119-121
website2/src/app/clean-air-forum/speakers/page.tsx (1)
22-26: Add TypeScript interfaces for person data structure.The filtering logic uses type 'any' which could lead to runtime errors. Let's add proper typing.
+interface Person { + id: string; + category: string; +} -const KeyNoteSpeakers = data?.persons?.filter( - (person: any) => +const KeyNoteSpeakers = data?.persons?.filter( + (person: Person) => -const Speakers = data?.persons?.filter( - (person: any) => +const Speakers = data?.persons?.filter( + (person: Person) =>Also applies to: 28-32
website2/src/app/clean-air-forum/partners/page.tsx (2)
18-47: Refactor partner filtering logic to reduce duplication.The partner filtering and mapping logic is repeated for each partner type. Let's create a utility function.
+const filterPartners = (partners: any[], category: string) => + partners?.filter(partner => partner.category === category) + .map(partner => ({ + id: partner.id, + logoUrl: partner.partner_logo_url, + })); -const conveningPartners = data.partners - ?.filter((partner: any) => partner.category === 'Co-Convening Partner') - .map((partner: any) => ({ - id: partner.id, - logoUrl: partner.partner_logo_url, - })); +const conveningPartners = filterPartners(data.partners, 'Co-Convening Partner');
105-105: Remove empty comment.The empty comment on line 105 should be removed.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
website2/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (8)
website2/package.json(1 hunks)website2/src/app/clean-air-forum/glossary/page.tsx(1 hunks)website2/src/app/clean-air-forum/logistics/page.tsx(3 hunks)website2/src/app/clean-air-forum/partners/page.tsx(6 hunks)website2/src/app/clean-air-forum/program-committee/page.tsx(2 hunks)website2/src/app/clean-air-forum/schedule/page.tsx(3 hunks)website2/src/app/clean-air-forum/speakers/page.tsx(2 hunks)website2/src/app/clean-air-forum/sponsorships/page.tsx(1 hunks)
🧰 Additional context used
🪛 Biome (1.9.4)
website2/src/app/clean-air-forum/sponsorships/page.tsx
[error] 30-30: Avoid passing content using the dangerouslySetInnerHTML prop.
Setting content using code can expose users to cross-site scripting (XSS) attacks
(lint/security/noDangerouslySetInnerHtml)
website2/src/app/clean-air-forum/schedule/page.tsx
[error] 90-90: Avoid passing content using the dangerouslySetInnerHTML prop.
Setting content using code can expose users to cross-site scripting (XSS) attacks
(lint/security/noDangerouslySetInnerHtml)
website2/src/app/clean-air-forum/glossary/page.tsx
[error] 81-81: Avoid passing content using the dangerouslySetInnerHTML prop.
Setting content using code can expose users to cross-site scripting (XSS) attacks
(lint/security/noDangerouslySetInnerHtml)
⏰ Context from checks skipped due to timeout of 90000ms (1)
- GitHub Check: build-push-website2-deploy-preview
🔇 Additional comments (5)
website2/src/app/clean-air-forum/logistics/page.tsx (1)
27-31: LGTM! Proper HTML sanitization implemented.Good job implementing DOMPurify to sanitize the HTML content before rendering, protecting against XSS attacks.
Also applies to: 48-52
🧰 Tools
🪛 Biome (1.9.4)
[error] 27-27: Avoid passing content using the dangerouslySetInnerHTML prop.
Setting content using code can expose users to cross-site scripting (XSS) attacks
(lint/security/noDangerouslySetInnerHtml)
website2/src/app/clean-air-forum/sponsorships/page.tsx (1)
30-35: LGTM! HTML content is properly sanitized.Good implementation of DOMPurify for sanitizing HTML content before rendering.
🧰 Tools
🪛 Biome (1.9.4)
[error] 30-30: Avoid passing content using the dangerouslySetInnerHTML prop.
Setting content using code can expose users to cross-site scripting (XSS) attacks
(lint/security/noDangerouslySetInnerHtml)
website2/src/app/clean-air-forum/program-committee/page.tsx (1)
55-59: LGTM! HTML content is properly sanitized.Good implementation of DOMPurify for sanitizing HTML content before rendering.
🧰 Tools
🪛 Biome (1.9.4)
[error] 55-55: Avoid passing content using the dangerouslySetInnerHTML prop.
Setting content using code can expose users to cross-site scripting (XSS) attacks
(lint/security/noDangerouslySetInnerHtml)
website2/src/app/clean-air-forum/glossary/page.tsx (1)
81-85: LGTM! HTML content is properly sanitized.Good implementation of DOMPurify for sanitizing HTML content before rendering.
🧰 Tools
🪛 Biome (1.9.4)
[error] 81-81: Avoid passing content using the dangerouslySetInnerHTML prop.
Setting content using code can expose users to cross-site scripting (XSS) attacks
(lint/security/noDangerouslySetInnerHtml)
website2/package.json (1)
30-30: LGTM! Dependencies updated appropriately.The addition of DOMPurify and the Next.js version update are appropriate for the changes being made.
Also applies to: 34-34
| const sponsorPartner = data.partners | ||
| ?.filter((partner: any) => partner.category === 'Sponsor Partner') | ||
| .map((partner: any) => ({ | ||
| id: partner.id, | ||
| logoUrl: partner.partner_logo_url, | ||
| })); |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Add type definitions for partner data.
Replace any type with proper interfaces to improve type safety and maintainability.
+interface Partner {
+ id: string;
+ category: string;
+ partner_logo_url: string;
+}
+
+interface SponsorPartner {
+ id: string;
+ logoUrl: string;
+}
- const sponsorPartner = data.partners
+ const sponsorPartner: SponsorPartner[] = data.partners
?.filter((partner: Partner) => partner.category === 'Sponsor Partner')
.map((partner: Partner) => ({
id: partner.id,
logoUrl: partner.partner_logo_url,
}));📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| const sponsorPartner = data.partners | |
| ?.filter((partner: any) => partner.category === 'Sponsor Partner') | |
| .map((partner: any) => ({ | |
| id: partner.id, | |
| logoUrl: partner.partner_logo_url, | |
| })); | |
| interface Partner { | |
| id: string; | |
| category: string; | |
| partner_logo_url: string; | |
| } | |
| interface SponsorPartner { | |
| id: string; | |
| logoUrl: string; | |
| } | |
| const sponsorPartner: SponsorPartner[] = data.partners | |
| ?.filter((partner: Partner) => partner.category === 'Sponsor Partner') | |
| .map((partner: Partner) => ({ | |
| id: partner.id, | |
| logoUrl: partner.partner_logo_url, | |
| })); |
| const router = useRouter(); | ||
| const dispatch = useDispatch(); | ||
| // Retrieve forum events and selected event index from Redux. | ||
| const { events, selectedEventIndex } = useSelector((state) => state.forum); |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Add type definitions for Redux state.
Define proper types for the Redux state to improve type safety.
+interface ForumEvent {
+ id: string;
+ title: string;
+ glossary_details: string;
+}
+
+interface ForumState {
+ events: ForumEvent[];
+ selectedEventIndex: number;
+}
- const { events, selectedEventIndex } = useSelector((state) => state.forum);
+ const { events, selectedEventIndex } = useSelector((state: { forum: ForumState }) => state.forum);📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| const { events, selectedEventIndex } = useSelector((state) => state.forum); | |
| +interface ForumEvent { | |
| + id: string; | |
| + title: string; | |
| + glossary_details: string; | |
| +} | |
| + | |
| +interface ForumState { | |
| + events: ForumEvent[]; | |
| + selectedEventIndex: number; | |
| +} | |
| - const { events, selectedEventIndex } = useSelector((state) => state.forum); | |
| + const { events, selectedEventIndex } = useSelector((state: { forum: ForumState }) => state.forum); |
|
New Website2 changes available for preview here |
Summary of Changes (What does this PR do?)
Status of maturity (all need to be checked before merging):
Screenshots (optional)
Summary by CodeRabbit
New Features
Bug Fixes
Refactor
Style
Chores