[WIP] Add TNTSearch

[mglaman]

For issue #218.

Test query bin/plugin tntsearch query "order placed"

Results. First one is the general requirement people need to find.

{
    "number_of_hits": 20,
    "execution_time": "2.094 ms",
    "hits": [
        {
            "link": "\/commerce2\/developer-guide\/orders\/react-to-workflow-transitions",
            "title": "Subscribing to Transition Events",
            "content": "...being used in commerce_<em>order<\/em> to set an <em>order<\/em>'s <em>placed<\/em> timestamp:\ncommerce_<em>order<\/em>.services.yml\nTimestampEventSubscriber.php\nFinding Transitions\nTransition information can be found in a {module}.workflows.yml.\nExample from commerce_<em>order<\/em>:\n # commerce_<em>order<\/em>.workflows.yml\n <em>order<\/em>_default:\n id:..."
        },
        {
            "link": "\/commerce2\/developer-guide\/orders",
            "title": "<em>Order<\/em>s",
            "content": "...]);\n $profile-&gt;save();\n\/\/ Next, we create the <em>order<\/em>.\n $<em>order<\/em> = \\Drupal\\commerce_<em>order<\/em>\\Entity\\<em>Order<\/em>::create([\n 'type' =&gt; 'custom_<em>order<\/em>_type',\n 'state' =&gt; 'draft',\n 'mail' =&gt; '[email protected]',\n 'uid' =&gt; 1,\n 'ip_address' =&gt; '127.0.0.1',\n '<em>order<\/em>_number' =&gt; '6',\n..."
        },
        {
            "link": "\/commerce2\/developer-guide\/orders\/workflows\/choosing-workflow",
            "title": "Choosing a workflow",
            "content": "...which is the Draft\/Cart state, then, once the <em>order<\/em> is <em>placed<\/em>, it is put in the Validation state. Once you're ready to ship the goods, the <em>order<\/em> is moved to the Fulfillment state. And finally, once it leaves our store, the <em>order<\/em> is officially Completed.\nNow, that you know the process, let's..."
        },
        {
            "link": "\/commerce2\/developer-guide\/orders\/create-custom-workflow",
            "title": "How to Create a Custom <em>Order<\/em> Workflow",
            "content": "...<em>order<\/em> and go to its View admin page. The <em>order<\/em> should be automatically put in the Processing state and you should be able to move it to the Fulfillment state by clicking the \"Process <em>order<\/em>\" button (indicating that the <em>order<\/em> has been processed), and then to the Completed state by clicking the..."
        },
        {
            "link": "\/commerce2\/developer-guide\/core\/libraries-and-dependencies\/state-machine",
            "title": "State Machine",
            "content": "...commerce_<em>order<\/em>.workflow_groups.yml:\n<em>order<\/em>:\n label: <em>Order<\/em>\n entity_type: commerce_<em>order<\/em>\nGroups can also override the default workflow class, for more advanced\nuse cases.\nExample: commerce_<em>order<\/em>.workflows.yml:\n<em>order<\/em>_default_validation:\n id: <em>order<\/em>_default_validation\n group: <em>order<\/em>\n label:..."
        },
        {
            "link": "\/commerce2\/developer-guide\/orders\/workflows\/workflow-transitions",
            "title": "<em>Order<\/em> workflow transitions",
            "content": "...by the Commerce <em>Order<\/em> module.\n\/\/ commerce_<em>order<\/em>.workflows.yml\n<em>order<\/em>_fulfillment:\n transitions:\n place:\n label: 'Place <em>order<\/em>'\n from: [draft]\n to: fulfillment\n fulfill:\n label: 'Fulfill <em>order<\/em>'\n from: [fulfillment]\n to: completed\n cancel:\n label: 'Cancel <em>order<\/em>'\n from: [draft, fulfillment]\n to:..."
        },
        {
            "link": "\/commerce2\/developer-guide\/checkout\/create-custom-checkout-flow",
            "title": "Creating a checkout flow plugin",
            "content": "...are going to use this checkout flow for future <em>order<\/em>s. To do that, go to\nadmin\/commerce\/config\/<em>order<\/em>-types\/default\/edit.\nAt the bottom you will see Checkout settings section. Select the checkout\nflow that you just created.\nClick Save.\nWhen the customers now place an <em>order<\/em>, they will just see the..."
        },
        {
            "link": "\/commerce2\/developer-guide\/payments\/off-site-redirect-gateways",
            "title": "Off-site (redirect) payment gateways",
            "content": "...'payment_gateway' =&gt; $this-&gt;entityId,\n '<em>order<\/em>_id' =&gt; $<em>order<\/em>-&gt;id(),\n 'remote_id' =&gt; $request-&gt;request-&gt;get('remote_id'),\n 'remote_state' =&gt; $request-&gt;request-&gt;get('remote_state'),\n ]);\n$payment-&gt;save();\n}\nThere are a couple of things to be aware of in the..."
        },
        {
            "link": "\/commerce1\/user-guide\/payments",
            "title": "Payments",
            "content": "...payment notification listener should update the <em>order<\/em> as necessary on receipt of the successful payment notification and use the API to move the <em>order<\/em> forward to the next checkout page.\nOff-site Payment Method Examples\nFor an example implementation, see the PayPal WPS module of the Commerce..."
        },
        {
            "link": "\/commerce1\/user-guide\/payments\/paypal-standard",
            "title": "PayPal Standard",
            "content": "...to your website once the payment is complete.\n<em>Order<\/em>s are still pending\n<em>Order<\/em>s will remain in the \"pending\" state unless the funds have been accepted by the seller using PayPal. In the sandbox, this means you would have to log into the developer master account, select the seller account, log..."
        },
        {
            "link": "\/commerce1\/user-guide\/managing-orders\/implementing-an-automated-order-workflow",
            "title": "Implementing an automated <em>order<\/em> workflow",
            "content": "...#### statuses and finally to the Pending <em>order<\/em> status. While the <em>Order<\/em> module defines additional <em>order<\/em> statuses for Canceled, Processing, and Completed <em>order<\/em>s, it does not implement any rules specifically to place <em>order<\/em>s into these statuses. The only way <em>order<\/em>s will get to these statuses..."
        },
        {
            "link": "\/commerce1\/user-guide\/customer-profiles",
            "title": "Customer Profiles",
            "content": "...This profile is then related to the customer's <em>order<\/em> via a customer profile reference field.\n<em>Order<\/em> edit form - each profile type is also represented on <em>order<\/em>s via default customer profile reference fields. These reference fields are populated by the relevant checkout panes but may also be filled..."
        },
        {
            "link": "\/commerce1\/user-guide\/checkout-process\/checkout-order-status-updates",
            "title": "Checkout <em>Order<\/em> Status Updates",
            "content": "...addition to customer data being saved to the <em>order<\/em>, the <em>order<\/em> status is also updated to reflect its current place in the checkout process. The checkout router uses the <em>order<\/em> status to determine a customer's access to visit a requested checkout page for a particular <em>order<\/em>.\nUpon checkout..."
        },
        {
            "link": "\/commerce1\/user-guide\/checkout-process\/checkout-completion-rules",
            "title": "Checkout Completion Rules",
            "content": "...method. But the event does happen, it just won't show a \"display message\" action.\n \n \n Administration\n Store\n Store Configuraiton\n <em>Order<\/em>s\n Edit <em>Order<\/em>\nTo get the event to fire in a way you can see, simply create an <em>order<\/em> and apply a payment manually.\n"
        },
        {
            "link": "\/commerce1\/developer-guide\/core-architecture\/systems\/customer-profile-system",
            "title": "Customer profile system",
            "content": "...This profile is then related to the customer's <em>order<\/em> via a customer profile reference field.\n<em>Order<\/em> edit form - each profile type is also represented on <em>order<\/em>s via default customer profile reference fields. These reference fields are populated by the relevant checkout panes but may also be filled..."
        },
        {
            "link": "\/commerce1\/developer-guide\/core-architecture\/info-hooks",
            "title": "Info Hooks",
            "content": "...In lists of properties, the unique key will be <em>placed<\/em> first and italicized. This key serves as the key in the array returned by the info hooks and is also present as a property on the object itself.\nCurrency info hooks\nPayment info hooks\nCheckout info hooks\nCustomer info hooks\nLine Item info..."
        },
        {
            "link": "\/commerce1\/developer-guide\/core-architecture\/info-hooks\/currency-info-hooks",
            "title": "Currency info hooks",
            "content": "...or 'after' indicating where the symbol is <em>placed<\/em> in relation to the amount of a price when formatted for the currency; if not specified, the symbol will not be displayed\ncode_placement - like symbol_placement but used for displaying the currency code\nformat_callback - function used for..."
        },
        {
            "link": "\/commerce2\/user-guide\/orders\/customer-emails",
            "title": "Receipt emails",
            "content": "...uncheck the Email the customer a receipt when an <em>order<\/em> is <em>placed<\/em> box.\nEnter the store notification email address into the Send a copy of the receipt to this email: field. You can enter multiple comma separated addresses into this field eg \"[email protected], [email protected],..."
        },
        {
            "link": "\/commerce2\/developer-guide\/orders\/order-refresh-and-process",
            "title": "<em>Order<\/em> refresh and processing",
            "content": "...<em>order<\/em> refresh cycle, controlled by the commerce_<em>order<\/em>.<em>order<\/em>_refresh process.\nThe <em>order<\/em> refresh process only runs on draft <em>order<\/em>s. It will not run on <em>order<\/em>s which have been <em>placed<\/em>.\nThe following is an overview of the process:\nAn <em>order<\/em> is loaded from storage and checked if it should be..."
        },
        {
            "link": "\/commerce2\/developer-guide\/promotions\/create-an-offer-type",
            "title": "Create an offer type",
            "content": "...adjustment is determined based on the entity (<em>order<\/em> or <em>order<\/em> item) values and the offer type configration values. Then a new \"promotion\" Adjustment is created and added to the entity.\nOffer type configuration\nOne part of creating a custom promotion offer plugin is to define the configuration..."
        }
    ]
}

[mglaman]

I guess this got merged somehow?