Add author filtering and CORS proxy for latest rules

[Aibono1225]

This pull request enhances the RulesWidget component to improve how it fetches and displays the latest rules for a given author.

Development environment improvements:

• Added an onCreateDevServer handler in gatsby-node.js to proxy requests for people-latest-rules.json during development, avoiding CORS issues by streaming the file from the production server.
• Added the axios dependency to support HTTP requests in the dev server proxy.

RulesWidget data handling and robustness:

• Refactored RulesWidget to fetch rule data from the new people-latest-rules.json endpoint, using the dev proxy path in development and the production URL otherwise.
• Introduced normalizeAuthor and pickRulesForAuthor helper functions to standardize author identifiers and reliably extract rules for the correct user from the JSON data, handling various input formats.
• Updated the widget to filter, sort, and limit the displayed rules per author, and to consistently use the normalized author for all lookups and links. [1] [2]

[Copilot]

Pull request overview

Adds author-based filtering for “Latest Rules” and introduces a Gatsby dev-server proxy endpoint to avoid CORS issues when developing locally.

Changes:

• Switch RulesWidget to fetch people-latest-rules.json, normalize the provided author, and select/sort rules for that author.
• Add a dev-only proxy route (/__rules/people-latest-rules.json) in gatsby-node.js that streams the upstream JSON to localhost during gatsby develop.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
src/components/rules-widget/rules-widget.js	Fetches the shared “people latest rules” JSON and filters it down to an author-specific list for display.
gatsby-node.js	Adds a onCreateDevServer route to proxy the rules JSON in development to bypass browser CORS.

Comments suppressed due to low confidence (1)

src/components/rules-widget/rules-widget.js:102

• catch (e) declares e but never uses it. This triggers no-unused-vars warnings, and the repo lint script uses --max-warnings=0 (so the build will fail). Use catch { ... } or handle/log the error variable.

            } catch (e) {
                if (!cancelled) {
                    setItems([]);
                    setStatus("error");
                }

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

catch (e) declares e but never uses it. With the repo's no-unused-vars set to warn and eslint run with --max-warnings=0, this will fail lint. Use optional catch binding (catch { ... }) or reference the error variable (e.g. log it) to avoid the unused var warning.

Suggested change

	} catch (e) {
	} catch {

[Aibono1225]

✅

[Copilot]

catch (e) declares e but never uses it, which triggers no-unused-vars warnings. Since the repo runs eslint with --max-warnings=0, this will fail lint. Prefer catch { ... } or otherwise use the error variable (e.g. include it in the response/logging).

Suggested change

	} catch (e) {
	} catch (e) {
	console.error('Failed to proxy rules JSON', e);

[Aibono1225]

✅

[Copilot]

upstream.data.pipe(res) doesn’t attach error/close handlers. If the upstream stream errors or the client disconnects, this can emit an unhandled stream error (or keep the upstream request open). Consider wiring upstream.data.on('error', …) and req.on('close', …) / res.on('close', …) to abort the upstream request and end the response cleanly.

Suggested change

	upstream.data.pipe(res);
	} catch (e) {
	res.status(500).json({ error: 'Failed to proxy rules JSON' });
	const cleanup = () => {
	const stream = upstream && upstream.data;
	if (stream && typeof stream.destroy === 'function' && !stream.destroyed) {
	stream.destroy();
	}
	};
	req.on('close', cleanup);
	res.on('close', cleanup);
	upstream.data.on('error', (err) => {
	cleanup();
	if (!res.headersSent) {
	res
	.status(502)
	.json({ error: 'Failed to proxy rules JSON from upstream' });
	} else {
	// If headers are already sent, just end the response.
	res.end();
	}
	});
	upstream.data.pipe(res);
	} catch (e) {
	if (!res.headersSent) {
	res.status(500).json({ error: 'Failed to proxy rules JSON' });
	} else {
	res.end();
	}

[Aibono1225]

✅