feat: update start date and end date as required since google api cha…

…nged its validation

README.md

@@ -55,13 +55,15 @@ required. it's your GA4 property id from Google Analytics Page.
 
 ### startDate
 
-required since v1.3.0. it's based on Google Analytics date value. Could be '30daysAgo', 'today', '
-yesterday', or ISO date format (yyyy-MM-dd) like '2022-12-31'.
+required since v1.3.0. it's based on Google Analytics date value. Could be '30daysAgo', 'today', 'yesterday', or ISO
+date format (yyyy-MM-dd) like '2022-12-31'. Default value '365daysAgo'. Google changed its API and for version < v1.3.0
+using startDate default value will throw error. Since v1.3.0 I encourage to specify your startDate in config or use
+dynamic value like '365daysAgo'.
 
 ### endDate
 
-required since v1.3.0. it's based on Google Analytics date value. Could be '30daysAgo', 'today', '
-yesterday', or ISO date format (yyyy-MM-dd) like '2022-12-31'.
+required since v1.3.0. it's based on Google Analytics date value. Could be '30daysAgo', 'today', 'yesterday', or ISO
+date format (yyyy-MM-dd) like '2022-12-31'. Default value 'today'. Since v1.3.0 I encourage to specify your endDate.
 
 ### metric
 

gatsby-node.js

@@ -29,7 +29,7 @@ exports.sourceNodes = async ({actions, createNodeId, createContentDigest}, plugi
     requestBody: {
       dimensions: [{name: "pagePath"}],
       metrics: [{name: metric}],
-      dateRanges: [{startDate: pluginOptions.startDate, endDate: pluginOptions.endDate}],
+      dateRanges: [{startDate: pluginOptions.startDate || '30daysAgo', endDate: pluginOptions.endDate || 'today'}],
       limit: pluginOptions.limit,
       orderBys: [{metric: {metricName: metric}, desc: pluginOptions.desc === true}],
     },

package.json

@@ -1,7 +1,7 @@
 {
   "name": "gatsby-plugin-google-analytics-data-reporting-api",
   "description": "Reporting API for Google Analytics 4 (GA4)",
-  "version": "1.3.0",
+  "version": "1.3.1",
   "main": "gatsby-node.js",
   "author": "Ferry Suhandri",
   "license": "MIT",