react_on_rails 13.4.0 → 14.0.1

data/docs/getting-started.md

@@ -1,196 +0,0 @@
-# Getting Started
-
-Note, the best way to understand how to use ReactOnRails is to study a few simple examples. You can do a quick demo setup, either on your existing app or on a new Rails app.
-
-This documentation assumes the usage of ReactOnRails with Shakapacker 7. For installation on Shakapacker 6, check [tips for usage with Shakapacker 6](https://www.shakacode.com/react-on-rails/docs/aditional-details/tips-for-usage-with-sp6) first.
-
-1. Do the quick [tutorial](https://www.shakacode.com/react-on-rails/docs/guides/tutorial/).
-2. Add React on Rails to an existing Rails app per [the instructions](https://www.shakacode.com/react-on-rails/docs/guides/installation-into-an-existing-rails-app/).
-3. Look at [spec/dummy](https://github.com/shakacode/react_on_rails/tree/master/spec/dummy), a simple, no DB example.
-3. Look at [github.com/shakacode/react-webpack-rails-tutorial](https://github.com/shakacode/react-webpack-rails-tutorial); it's a full-featured example live at [www.reactrails.com](http://reactrails.com).
-
-## Basic Installation
-
-You need a Rails application with Shakapacker installed and configured on it. Check [Shakapacker documentation](https://github.com/shakacode/shakapacker) for more details but typically you need the following steps:
-
-```bash
-rails new PROJECT_NAME --skip-javascript
-cd PROJECT_NAME
-bundle add shakapacker --strict
-rails shakapacker:install
-```
-
-You may need to check [the instructions for installing into an existing Rails app](https://www.shakacode.com/react-on-rails/docs/guides/installation-into-an-existing-rails-app/) if you have an already working Rails application.
-
-1. Add the `react_on_rails` gem to Gemfile:
-
-   ```bash
-   bundle add react_on_rails --strict
-   ```
-
-   Commit this to git (or else you cannot run the generator in the next step unless you pass the option `--ignore-warnings`).
-
-2. Run the install generator:
-
-   ```bash
-   rails generate react_on_rails:install
-   ```
-
-3. Start the app:
-
-   - Run `./bin/dev` for HMR
-   - Run `./bin/dev-static` for statically created bundles (no HMR)
-
-4. Visit http://localhost:3000/hello_world.
-
-
-### Turning on server rendering
-
-With the code from running the React on Rails generator above:
-
-1. Edit `app/views/hello_world/index.html.erb` and set the `prerender` option to `true`.
-
-    You may need to use `Node` as your js runtime environment by setting `EXECJS_RUNTIME=Node` into your environment variables.
-
-2. Refresh the page.
-
-Below is the line where you turn server rendering on by setting `prerender` to true:
-
-```erb
-<%= react_component("HelloWorld", props: @hello_world_props, prerender: true) %>
-```
-
-Note, if you got an error in your console regarding "ReferenceError: window is not defined",
-then you need to edit `config/shakapacker.yml` and set `hmr: false` and `inline: false`.
-See [rails/webpacker PR 2644](https://github.com/rails/webpacker/pull/2644) for a fix for this
-issue.
-
-## Basic Usage
-
-### Configuration
-
-* Configure `config/initializers/react_on_rails.rb`. You can adjust some necessary settings and defaults. See file [docs/basics/configuration.md](https://www.shakacode.com/react-on-rails/docs/guides/configuration/) for documentation of all configuration options.
-* Configure `config/shakapacker.yml`. If you used the generator and the default Shakapacker setup, you don't need to touch this file. If you are customizing your setup, then consult the [spec/dummy/config/shakapacker.yml](https://github.com/shakacode/react_on_rails/tree/master/spec/dummy/config/shakapacker.yml) example or the official default [shakapacker.yml](https://github.com/shakacode/shakapacker/blob/master/lib/install/config/shakapacker.yml).
-* Most apps should rely on the Shakapacker setup for Webpack. Shakapacker v6+ includes support for webpack version 5.
-
-## Including your React Component on your Rails Views
-
-- React components are rendered via your Rails Views. Here's an ERB sample:
-
-  ```erb
-  <%= react_component("HelloWorld", props: @some_props) %>
-  ```
-
-- **Server-Side Rendering**: Your React component is first rendered into HTML on the server. Use the **prerender** option:
-
-  ```erb
-  <%= react_component("HelloWorld", props: @some_props, prerender: true) %>
-  ```
-
-- The `component_name` parameter is a string matching the name you used to expose your React component globally. So, in the above examples, if you had a React component named "HelloWorld", you would register it with the following lines:
-
-  ```js
-  import ReactOnRails from 'react-on-rails';
-  import HelloWorld from './HelloWorld';
-  ReactOnRails.register({ HelloWorld });
-  ```
-
-  Exposing your component in this way is how React on Rails is able to reference your component from a Rails view. You can expose as many components as you like, as long as their names do not collide. See below for the details of how you expose your components via the react_on_rails webpack configuration. You may call `ReactOnRails.register` many times.
-
-- `@some_props` can be either a hash or JSON string. This is an optional argument assuming you do not need to pass any options (if you want to pass options, such as `prerender: true`, but you do not want to pass any properties, simply pass an empty hash `{}`). This will make the data available in your component:
-
-  ```ruby
-    # Rails View
-    <%= react_component("HelloWorld", props: { name: "Stranger" }) %>
-  ```
-
-- This is what your HelloWorld.js file might contain. The railsContext is always available for any parameters that you _always_ want available for your React components. It has _nothing_ to do with the concept of the [React Context](https://reactjs.org/docs/context.html). See [Render-Functions and the RailsContext](https://www.shakacode.com/react-on-rails/docs/guides/render-functions-and-railscontext/) for more details on this topic.
-
-  ```js
-  import React from 'react';
-
-  export default (props, railsContext) => {
-    // Note wrap in a function to make this a React function component
-    return () => (
-      <div>
-        Your locale is {railsContext.i18nLocale}.<br/>
-        Hello, {props.name}!
-      </div>
-    );
-  };
-  ```
-
-See the [View Helpers API](https://www.shakacode.com/react-on-rails/docs/api/view-helpers-api/) for more details on `react_component` and its sibling function `react_component_hash`.
-
-## Globally Exposing Your React Components
-
-For the React on Rails view helper `react_component` to use your React components, you will have to **register** them in your JavaScript code.
-
-Use modules just as you would when using Webpack and React without Rails. The difference is that instead of mounting React components directly to an element using `React.render`, you **register your components to ReactOnRails and then mount them with helpers inside of your Rails views**.
-
-This is how to expose a component to the `react_component` view helper.
-
-```javascript
-  // app/javascript/packs/hello-world-bundle.js
-  import HelloWorld from '../components/HelloWorld';
-  import ReactOnRails from 'react-on-rails';
-  ReactOnRails.register({ HelloWorld });
-```
-
-#### Different Server-Side Rendering Code (and a Server-Specific Bundle)
-
-You may want different code for your server-rendered components running server side versus client side. For example, if you have an animation that runs when a component is displayed, you might need to turn that off when server rendering. One way to handle this is conditional code like `if (window) { doClientOnlyCode() }`.
-
-Another way is to use a separate webpack configuration file that can use a different server side entry file, like  'serverRegistration.js' as opposed to 'clientRegistration.js.' That would set up different code for server rendering.
-
-For details on techniques to use different code for client and server rendering, see: [How to use different versions of a file for client and server rendering](https://forum.shakacode.com/t/how-to-use-different-versions-of-a-file-for-client-and-server-rendering/1352). (_Requires creating a free account._)
-
-## Specifying Your React Components: Register directly or use render-functions
-
-You have two ways to specify your React components. You can either register the React component (either function or class component) directly, or you can create a function that returns a React component, which we using the name of a "render-function". Creating a render-function allows you to:
-
-1. Access to the `railsContext`. See the [documentation for the railsContext](https://www.shakacode.com/react-on-rails/docs/guides/render-functions-and-railscontext/) in terms of why you might need it. You **need** a Render-Function to access the `railsContext`.
-2. Use the passed-in props to initialize a redux store or set up `react-router`.
-3. Return different components depending on what's in the props.
-
-Note, the return value of a **Render-Function** should be either a React Function or Class Component or an object representing server rendering results.
-
-**Do not return a React Element (JSX).**
-
-ReactOnRails will automatically detect a registered Render-Function by the fact that the function takes
-more than 1 parameter. In other words, if you want the ability to provide a function that returns the
-React component, then you need to specify at least a second parameter. This is the `railsContext`.
-If you're not using this parameter, declare your function with the unused param:
-
-```js
-const MyComponentGenerator = (props, _railsContext) => {
-  if (props.print) {
-    // This is a React FunctionComponent because it is wrapped in a function.
-    return () => <H1>{JSON.stringify(props)}</H1>;
-  }
-}
-```
-
-Thus, there is no difference between registering a React Function Component or class Component versus a "Render-Function." Just call `ReactOnRails.register`.
-
-## react_component_hash for Render-Functions
-
-Another reason to use a Render-Function is that sometimes in server rendering, specifically with React Router, you need to return the result of calling ReactDOMServer.renderToString(element). You can do this by returning an object with the following shape: `{ renderedHtml, redirectLocation, error }`. Make sure you use this function with `react_component_hash`.
-
-For server rendering, if you wish to return multiple HTML strings from a Render-Function, you may return an Object from your Render-Function with a single top-level property of `renderedHtml`. Inside this Object, place a key called `componentHtml`, along with any other needed keys. An example scenario of this is when you are using side effects libraries like [React Helmet](https://github.com/nfl/react-helmet). Your Ruby code will get this Object as a Hash containing keys `componentHtml` and any other custom keys that you added:
-
-```js
-{ renderedHtml: { componentHtml, customKey1, customKey2} }
-```
-
-For details on using react_component_hash with react-helmet, see [our react-helmet documentation](https://www.shakacode.com/react-on-rails/docs/additional-reading/react-helmet/).
-
-## Error Handling
-
-* All errors from ReactOnRails will be of type ReactOnRails::Error.
-* Prerendering (server rendering) errors get context information for HoneyBadger and Sentry for easier debugging.
-
-## I18n
-
-React on Rails provides an option for automatic conversions of Rails `*.yml` locale files into `*.json` or `*.js*.
-See the [How to add I18n](https://www.shakacode.com/react-on-rails/docs/guides/i18n/) for a summary of adding I18n.

data/docs/guides/client-vs-server-rendering.md

@@ -1,27 +0,0 @@
-# Client-Side Rendering vs. Server-Side Rendering
-
-*Also, see [our react server-rendering documentation](https://www.shakacode.com/react-on-rails/docs/guides/react-server-rendering/).*
-
-In most cases, you should use the `prerender: false` (default behavior) with the provided helper method to render the React component from your Rails views. In some cases, such as when SEO is vital, or many users will not have JavaScript enabled, you can enable server-rendering by passing `prerender: true` to your helper, or you can simply change the default in `config/initializers/react_on_rails`.
-
-Now the server will interpret your JavaScript. The default is to use [ExecJS](https://github.com/rails/execjs) and pass the resulting HTML to the client. By default, ExecJS uses the Node.js runtime. You can use alternative runtimes as outlined in [ExecJS readme](https://github.com/rails/execjs/blob/master/README.md).
-
-Note: if you use the [mini_racer](https://github.com/rubyjs/mini_racer) runtime and run into a `ReferenceError: TextEncoder is not defined` error, see [this comment](https://github.com/shakacode/react_on_rails/issues/1457#issuecomment-1165026717) for a solution.
-
-If you want to maximize the performance of your server rendering, then you want to use React on Rails Pro which uses NodeJS to do the server rendering. See the [docs for React on Rails Pro](https://github.com/shakacode/react_on_rails/wiki).
-
-If you open the HTML source of any web page using React on Rails, you'll see the 3 parts of React on Rails rendering:
-
-1. A script tag containing the properties of the React component, such as the registered name and any props. A JavaScript function runs after the page loads, using this data to build and initialize your React components.
-2. The wrapper div `<div id="HelloWorld-react-component-0">` specifies the div where to place the React rendering. It encloses the server-rendered HTML for the React component.
-3. Additional JavaScript is placed to console-log any messages, such as server rendering errors. Note: these server side logs can be configured only to be sent to the server logs.
-
-**Note**: If server rendering is not used (prerender: false), then the major difference is that the HTML rendered for the React component only contains the outer div: `<div id="HelloWorld-react-component-0"/>`. The first specification of the React component is just the same.
-
-# Different Server-Side Rendering Code (and a Server-Specific Bundle)
-
-You may want different code for your server-rendered components running server side versus client side. For example, if you have an animation that runs when a component is displayed, you might need to turn that off when server rendering. One way to handle this is conditional code like `if (window) { doClientOnlyCode() }`.
-
-Another way is to use a separate webpack configuration file that can use a different server side entry file, like  'serverRegistration.js' as opposed to 'clientRegistration.js.' That would set up different code for server rendering.
-
-For details on techniques to use different code for client and server rendering, see: [How to use different versions of a file for client and server rendering](https://forum.shakacode.com/t/how-to-use-different-versions-of-a-file-for-client-and-server-rendering/1352). _Requires creating a free account._

data/docs/guides/configuration.md

@@ -1,289 +0,0 @@
-Here is the full set of config options. This file is `/config/initializers/react_on_rails.rb`
-
-First, you should have a `/config/shakapacker.yml` setup.
-
-Here is the setup when using the recommended `/client` directory for your `node_modules` and source files:
-
-```yaml
-# Note: Base output directory of /public is assumed for static files
-default: &default
-  compile: false
-  # Used in your webpack configuration. Must be created in the
-  # public_output_path folder
-  manifest: manifest.json
-  cache_manifest: false
-
-  # Source path is used to check if webpack compilation needs to be run for `compile: true`
-  source_path: client/app
-
-development:
-  <<: *default
-  # Generated files for development, in /public/webpack/dev
-  public_output_path: webpack/dev
-
-test:
-  <<: *default
-  # Ensure that shakapacker invokes webpack to build files for tests if not using the
-  #   ReactOnRails rspec helper.
-  compile: true
-
-  # Generated files for tests, in /public/webpack/test
-  public_output_path: webpack/test
-
-production:
-  <<: *default
-  # Generated files for production, in /public/webpack/production
-  public_output_path: webpack/production
-  cache_manifest: true
-```
-
-Here's a representative `/config/initializers/react_on_rails.rb` setup when using this `/client` directory
-for all client files, including your sources and node_modules.
-
-
-```ruby
-# frozen_string_literal: true
-
-# NOTE: you typically will leave the commented out configurations set to their defaults.
-# Thus, you only need to pay careful attention to the non-commented settings in this file.
-ReactOnRails.configure do |config|
-  # You can optionally add values to your rails_context. This object is passed
-  # every time a component renders.
-  # See below for an example definition of RenderingExtension
-  config.rendering_extension = RenderingExtension
-  
-  # `trace`: General debugging flag.
-  # The default is true for development, off otherwise.
-  # With true, you get detailed logs of rendering and stack traces if you call setTimout,
-  # setInterval, clearTimout when server rendering.
-  config.trace = Rails.env.development? # default
-
-  # Configure if default DOM IDs have a random value or are fixed.
-  # false ==> Sets the dom id to "#{react_component_name}-react-component"
-  # true ==> Adds "-#{SecureRandom.uuid}" to that ID
-  # If you might use multiple instances of the same React component on a Rails page, then
-  # it is convenient to set this to true or else you have to either manually set the ids to
-  # avoid collisions. Most newer apps will have only one instance of a component on a page,
-  # so this should be false in most cases.
-  # This value can be overridden for a given call to react_component
-  config.random_dom_id = true # default
-
-  # defaults to "" (top level)
-  config.node_modules_location = "client" # If using Shakapacker you should use "".
-
-  # If you're using the standard Shakapacker configuration of webpack, then Shakapacker
-  # will automatically modify or create an assets:precompile task to build your assets. If so,
-  # set this value to nil.  Alternatively, you can specify `config.build_production_command`
-  # to have react_on_rails invoke a command for you during assets:precompile.
-  # The command is either a script or a module containing a class method `call`
-  # In this example, the module BuildProductionCommand would have a class method `call`.
-  config.build_production_command = "RAILS_ENV=production bin/shakapacker"
-
-  # NOTE:
-  # When specifying `build_production_command`, you need to disable `rails/shakapacker` 
-  # configuration by setting `shakapacker_precompile: false` in your `config/shakapacker.yml` file.
-
-  # See bottom for an example of the BuildProductionCommand module.
-  # config.build_production_command = BuildProductionCommand
-  # If you wish to utilize ReactOnRailsPro production bundle caching logic, then use
-  # config.build_production_command = ReactOnRailsPro::AssetsPrecompile
-  # and be sure to check ReactOnRailsPro's configuration documentation!
-
-  ################################################################################
-  ################################################################################
-  # SERVER RENDERING OPTIONS
-  ################################################################################
-  # This is the file used for server rendering of React when using `(prerender: true)`
-  # If you are not using server rendering, you should set this to `nil`.
-  # Note, there is only one server bundle, unlike JavaScript where you want to minimize the size
-  # of the JS sent to the client. For the server rendering, React on Rails creates a pool of
-  # JavaScript execution instances which should handle any component requested.
-  #
-  # While you may configure this to be the same as your client bundle file, this file is typically
-  # different. Note, be sure to include the exact file name with the ".js" if you are not hashing this file.
-  # If you are hashing this file (supposing you are using the same file for client rendering), then
-  # you should include a name that matches your bundle name in your webpack config.
-  config.server_bundle_js_file = "server-bundle.js"
-  
-  # `prerender` means server-side rendering
-  # default is false. This is an option for view helpers `render_component` and `render_component_hash`.
-  # Set to true to change the default value to true. 
-  config.prerender = false
-
-  # THE BELOW OPTIONS FOR SERVER-SIDE RENDERING RARELY NEED CHANGING
-  #
-  # This value only affects server-side rendering when using the webpack-dev-server
-  # If you are hashing the server bundle and you want to use the same bundle for client and server,
-  # you'd set this to `true` so that React on Rails reads the server bundle from the webpack-dev-server.
-  # Normally, you have different bundles for client and server, thus, the default is false.
-  # Furthermore, if you are not hashing the server bundle (not in the manifest.json), then React on Rails
-  # will only look for the server bundle to be created in the typical file location, typically by
-  # a `shakapacker --watch` process.
-  # If true, ensure that in config/shakapacker.yml that you have both dev_server.hmr and
-  # dev_server.inline set to false.
-  config.same_bundle_for_client_and_server = false
-
-  # If set to true, this forces Rails to reload the server bundle if it is modified
-  # Default value is Rails.env.development?
-  # You probably will never change this.
-  config.development_mode = Rails.env.development?
-
-  # For server rendering so that the server-side console replays in the browser console.
-  # This can be set to false so that server side messages are not displayed in the browser.
-  # Default is true. Be cautious about turning this off, as it can make debugging difficult.
-  # Default value is true
-  config.replay_console = true
-
-  # Default is true. Logs server rendering messages to Rails.logger.info. If false, you'll only
-  # see the server rendering messages in the browser console.
-  config.logging_on_server = true
-
-  # Default is true only for development? to raise exception on server if the JS code throws for
-  # server rendering. The reason is that the server logs will show the error and force you to fix
-  # any server rendering issues immediately during development.
-  config.raise_on_prerender_error = Rails.env.development?
-
-  # This configuration allows logic to be applied to client rendered props, such as stripping props that are only used during server rendering.
-  # Add a module with an adjust_props_for_client_side_hydration method that expects the component's name & props hash
-  # See below for an example definition of RenderingPropsExtension
-  config.rendering_props_extension = RenderingPropsExtension
-
-  ################################################################################
-  # Server Renderer Configuration for ExecJS
-  ################################################################################
-  # The default server rendering is ExecJS, by default using Node.js runtime
-  # If you wish to use an alternative Node server rendering for higher performance,
-  # contact justin@shakacode.com for details.
-  #
-  # For ExecJS:
-  # You can configure your pool of JS virtual machines and specify where it should load code:
-  # On MRI, use `node.js` runtime for the best performance
-  # (see https://github.com/shakacode/react_on_rails/issues/1438)
-  # Also see https://github.com/shakacode/react_on_rails/issues/1457#issuecomment-1165026717 if using `mini_racer`
-  # On MRI, you'll get a deadlock with `pool_size` > 1
-  # If you're using JRuby, you can increase `pool_size` to have real multi-threaded rendering.
-  config.server_renderer_pool_size = 1 # increase if you're on JRuby
-  config.server_renderer_timeout = 20 # seconds
-
-  ################################################################################
-  ################################################################################
-  # FILE SYSTEM BASED COMPONENT REGISTRY
-  # `render_component` and `render_component_hash` view helper methods can
-  # auto-load the bundle for the generated component, to avoid having to specify the
-  # bundle manually for each view with the component.
-  ################################################################################
-  # components_subdirectory is the name of the subdirectory matched to detect and register components automatically
-  # The default is nil. You can enable the feature by updating it in the next line.
-  config.components_subdirectory = nil
-  # Change to a value like this example to enable this feature 
-  # config.components_subdirectory = "ror_components"
-
-  # Default is false.
-  # The default can be overidden as an option in calls to view helpers
-  # `render_component` and `render_component_hash`. You may set to true to change the default to auto loading.
-  config.auto_load_bundle = false
-
-  # Default is false
-  # Set this to true & instead of trying to import the generated server components into your existing
-  # server bundle entrypoint, the PacksGenerator will create a server bundle entrypoint using
-  # config.server_bundle_js_file for the filename.
-  config.make_generated_server_bundle_the_entrypoint = false
-
-  # Default is true, which matches Webpacker/Shakapacker's defer default for `append_javascript_pack`
-  # Set this to false to have `defer: false` added to your `append_javascript_pack` calls for generated entrypoints.
-  config.defer_generated_component_packs = true
-
-  ################################################################################
-  # I18N OPTIONS
-  ################################################################################
-  # Replace the following line to the location where you keep translation.js & default.js for use
-  # by the npm packages react-intl. Be sure this directory exists!
-  # config.i18n_dir = Rails.root.join("client", "app", "libs", "i18n")
-  #
-  # If not using the i18n feature, then leave this section commented out or set the value
-  # of config.i18n_dir to nil.
-  #
-  # Replace the following line to the location where you keep your client i18n yml files
-  # that will source for automatic generation on translations.js & default.js
-  # By default(without this option) all yaml files from Rails.root.join("config", "locales")
-  # and installed gems are loaded
-  config.i18n_yml_dir = Rails.root.join("config", "locales")
-
-  # Possible output formats are js and json
-  # The default format is json
-  config.i18n_output_format = 'json'
-
-  ################################################################################
-  ################################################################################
-  # TEST CONFIGURATION OPTIONS
-  # Below options are used with the use of this test helper:
-  # ReactOnRails::TestHelper.configure_rspec_to_compile_assets(config)
-  #
-  # NOTE:
-  # Instead of using this test helper, you may ensure fresh test files using Shakapacker via:
-  # 1. Have `config/webpack/test.js` exporting an array of objects to configure both client and server bundles.
-  # 2. Set the compile option to true in config/shakapacker.yml for env test
-  ################################################################################
-
-  # If you are using this in your spec_helper.rb (or rails_helper.rb):
-  #
-  # ReactOnRails::TestHelper.configure_rspec_to_compile_assets(config)
-  #
-  # with rspec then this controls what yarn command is run
-  # to automatically refresh your webpack assets on every test run.
-  #
-  config.build_test_command = "RAILS_ENV=test bin/shakapacker"
-
-  # CONFIGURE YOUR SOURCE FILES
-  # The test helper needs to know where your JavaScript files exist. The value is configured
-  # by your config/shakapacker.yml source_path:
-  # source_path: client/app # if using recommended /client directory
-  #
-  # Define the files we need to check for webpack compilation when running tests.
-  # The default is `%w( manifest.json )` as will be sufficient for most shakapacker builds.
-  # However, if you are generating a server bundle that is NOT hashed (present in manifest.json),
-  # then include the file in this list like this:
-  config.webpack_generated_files = %w( server-bundle.js manifest.json )
-  # Note, be sure NOT to include your server-bundle.js if it is hashed, or else React on Rails will
-  # think the server-bundle.js is missing every time for test runs.
-end
-```
-
-Example of a ReactOnRailsConfig module for `client_props_extension`:
-
-```ruby
-module RenderingPropsExtension
-  # The modify_props method will be called by ReactOnRails::ReactComponent::RenderOptions if config.client_props_extension is defined
-  def self.adjust_props_for_client_side_hydration(component_name, props)
-    component_name == 'HelloWorld' ? props.except(:server_side_only) : props
-  end
-end
-```
-
-Example of a ReactOnRailsConfig module for `production_build_command`:
-
-```ruby
-module BuildProductionCommand
-  include FileUtils
-  # The call method will be called during assets:precompile
-  def self.call
-    sh "bin/shakapacker"
-  end
-end
-```
-
-Example of a RenderingExtension for custom values in the `rails_context`:
-
-```ruby
-module RenderingExtension
-
-  # Return a Hash that contains custom values from the view context that will get merged with
-  # the standard rails_context values and passed to all calls to Render-Functions used by the
-  # react_component and redux_store view helpers
-  def self.custom_context(view_context)
-    {
-     somethingUseful: view_context.session[:something_useful]
-    }
-  end
-end
-```

data/docs/guides/deployment.md

@@ -1,5 +0,0 @@
-# Deployment
-
-Shakapacker puts the necessary precompile steps automatically in the rake precompile step.
-
-See the [Heroku Deployment](https://www.shakacode.com/react-on-rails/docs/deployment/heroku-deployment/) doc for specifics regarding Heroku. The information for Heroku may apply to other deployments.