refactor: make renderRequestId optional in server component rendering for improved flexibility and clarity

Author: AbanoubGhadban

lib/react_on_rails/react_component/render_options.rb

@@ -21,7 +21,8 @@ def initialize(react_component_name: required("react_component_name"), options:
         # Therefore, we need an additional unique identifier that can be used both on the client and server.
         # This ID can also be used to associate specific data with a particular rendered component
         # on either the server or client.
-        @render_request_id = self.class.generate_request_id
+        # This ID is only present if RSC support is enabled because it's only used in that case.
+        @render_request_id = self.class.generate_request_id if ReactOnRails::Utils.rsc_support_enabled?
       end
 
       attr_reader :react_component_name, :render_request_id

lib/react_on_rails/server_rendering_js_code.rb

@@ -38,7 +38,6 @@ def render(props_string, rails_context, redux_stores, react_component_name, rend
         <<-JS
         (function() {
           var railsContext = #{rails_context};
-          railsContext.componentSpecificMetadata = {renderRequestId: '#{render_options.render_request_id}'};
         #{redux_stores}
           var props = #{props_string};
           return ReactOnRails.serverRenderReactComponent({

node_package/src/ClientSideRenderer.ts

@@ -85,16 +85,16 @@ class ComponentRenderer {
     const trace = el.getAttribute('data-trace') === 'true';
     const renderRequestId = el.getAttribute('data-render-request-id');
 
-    if (!renderRequestId) {
-      console.error(`renderRequestId is missing for component ${name} in the DOM node with id ${domNodeId}`);
-    }
-
-    const componentSpecificRailsContext = {
-      ...railsContext,
-      componentSpecificMetadata: {
-        renderRequestId: renderRequestId || '',
-      },
-    };
+    // The renderRequestId is optional and only present when React Server Components (RSC) support is enabled.
+    // When RSC is enabled, this ID helps track and associate server-rendered components with their client-side hydration.
+    const componentSpecificRailsContext = renderRequestId
+      ? {
+          ...railsContext,
+          componentSpecificMetadata: {
+            renderRequestId,
+          },
+        }
+      : railsContext;
 
     try {
       const domNode = document.getElementById(domNodeId);