Skip to content

Add activity feed API #44

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.

Sign up for GitHub

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

Draft
bniladridas wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Add activity feed API #44

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions graphite-demo/server.js
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
const express = require('express');
const app = express();
const port = 3000;
Comment on lines +1 to +3
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot Jan 11, 2026

Choose a reason for hiding this comment

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

high

There are a couple of improvements that can be made to the initial server setup:

  1. Security: It's highly recommended to use middleware like helmet. It sets various security-related HTTP headers that can protect your application from common web vulnerabilities. You'll need to add helmet as a dependency (npm install helmet).
  2. Configuration: The port is hardcoded. It's a best practice to use environment variables for configuration like port numbers. This provides flexibility for deployment across different environments (development, production, etc.).
const express = require('express');
const helmet = require('helmet');

const app = express();
app.use(helmet());

const port = process.env.PORT || 3000;


// Fake data for the activity feed
const activityFeed = [
{
id: 1000,
title: 'New Photo Uploaded',
body: 'Alice uploaded a new photo to her album.'
},
{
id: 2000,
title: 'Comment on Post',
body: "Bob commented on Charlie's post."
},
{
id: 13,
title: 'Status Update',
body: 'Charlie updated their status: "Excited about the new project!"'
}
];

app.get('/feed', (req, res) => {
res.json(activityFeed);
});
Comment on lines +24 to +26
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot Jan 11, 2026

Choose a reason for hiding this comment

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

medium

The route handler currently lacks error handling. While the current implementation is simple, it's a good practice to wrap the logic in a try...catch block. This makes the API more robust and will prevent the server from crashing due to unhandled exceptions as the logic grows more complex (e.g., fetching data from a database).

app.get('/feed', (req, res) => {
  try {
    res.json(activityFeed);
  } catch (error) {
    console.error('Error fetching activity feed:', error);
    res.status(500).json({ message: 'Internal Server Error' });
  }
});


app.listen(port, () => {
console.log(`Server running on port ${port}`);
});
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot Jan 11, 2026

Choose a reason for hiding this comment

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

medium

It's a common convention and best practice to end files with a newline character. Many tools and editors expect this, and it can help prevent issues with file concatenation and diffs.

});

Loading