components/polygon/polygon.app.mjs (3)

7-44: Consider adding a default value for adjusted.
Since "By default, results are adjusted" per the description, you may wish to explicitly set default: true for the adjusted prop to prevent future ambiguity and ensure consistent behavior if the user doesn't select a value.

---

46-62: Add explicit error handling to _makeRequest.
Returning raw responses from APIs can obscure root causes when requests fail. Consider wrapping your axios call in a try/catch block to handle and log errors more gracefully.

---

113-141: Prevent potential infinite loop in pagination.
Consider implementing an iteration boundary or a timeout if parseDataFn or the API incorrectly returns a nextPage for all pages. This ensures the loop won't run indefinitely in the event of unexpected responses.

components/polygon/common/utils.mjs (1)

1-7: Handle invalid URL scenarios gracefully.
If nextUrl is sometimes malformed, calling new URL(nextUrl) may throw an error. Checking for valid URLs beforehand or wrapping it in a try/catch could help prevent unexpected runtime failures.

components/polygon/sources/new-market-news/new-market-news.mjs (1)

24-27: Consider adjusting the limit parameter.

Setting a high limit of 1000 items per request might impact performance and memory usage.

Consider reducing the limit and relying on pagination:

-          "limit": 1000,
+          "limit": 100,

components/polygon/sources/new-stock-trade/new-stock-trade.mjs (1)

33-35: Add price formatting.

The price in the summary should be formatted for better readability.

-      return `New trade for ${item.sym} at $${item.p}`;
+      return `New trade for ${item.sym} at $${item.p.toFixed(2)}`;

components/polygon/sources/new-stock-price-summary/new-stock-price-summary.mjs (2)

34-35: Consider adjusting the limit parameter.

Setting a high limit of 5000 items per request might impact performance and memory usage.

Consider reducing the limit and relying on pagination:

-          "limit": 5000,
+          "limit": 100,

---

27-29: Enhance summary with price information.

The summary could be more informative by including the actual price data.

-    getSummary() {
-      return `Daily price summary for ${this.stockTicker}`;
+    getSummary(item) {
+      return `Daily price summary for ${this.stockTicker}: Open $${item.o.toFixed(2)}, Close $${item.c.toFixed(2)}`;
     },

components/polygon/sources/common/base.mjs (2)

37-37: Use a more reliable date comparison method.

Date.parse() can be unreliable with certain date formats. Consider using a date parsing library like date-fns or moment.js for more robust date handling.

---

46-46: Consider timezone handling in timestamp fallback.

The fallback to new Date() doesn't consider timezone differences. Consider using UTC dates consistently.

-          const ts = Date.parse(item.published_utc || item.sip_timestamp || new Date());
+          const ts = Date.parse(item.published_utc || item.sip_timestamp || new Date().toISOString());

components/polygon/actions/get-company-financials/get-company-financials.mjs (2)

24-28: Improve description formatting.

The filing date description uses template literals with manual line breaks. Consider using a more maintainable format.

-      description: `Query by the date when the filing with financials data was filed in **YYYY-MM-DD** format.
-                  \nBest used when querying over date ranges to find financials based on filings that happen in a time period.
-                  \nExamples:
-                  \nTo get financials based on filings that have happened after January 1, 2009 use the query param filing_date.gte=2009-01-01
-                  \nTo get financials based on filings that happened in the year 2009 use the query params filing_date.gte=2009-01-01&filing_date.lt=2010-01-01`,
+      description: [
+        "Query by the date when the filing with financials data was filed in **YYYY-MM-DD** format.",
+        "Best used when querying over date ranges to find financials based on filings that happen in a time period.",
+        "Examples:",
+        "- To get financials based on filings that have happened after January 1, 2009 use the query param filing_date.gte=2009-01-01",
+        "- To get financials based on filings that happened in the year 2009 use the query params filing_date.gte=2009-01-01&filing_date.lt=2010-01-01"
+      ].join("\n"),

---

71-79: Simplify params object structure.

The params object includes the stockTicker which could be passed directly to the API call.

     const financialDetails = await this.polygon.getFinancialDetails({
       $,
+      stockTicker: this.stockTicker,
       params: {
-        stockTicker: this.stockTicker,
         filingDate: this.filingDate,
         periodOfReportDate: this.periodOfReportDate,
         timeframe: this.timeframe,
         order: this.order,
         limit: this.limit,
         sort: this.sort,
       },
     });

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