f084fe3a31
* feat(askai): add Kapa.ai source group filtering for InfluxDB v3 - Add ai_source_group_ids field to all InfluxDB v3 products in data/products.yml - Add getProductSourceGroupIds() function to retrieve source group IDs from product data - Enables filtered AI responses using Kapa source groups for documentation pages - Follows existing pattern for dynamic product configuration - Implement version-specific config support (__v1, __v2 suffixes) - Append version hints to example questions for InfluxDB database products only - Make example questions generic (remove product-specific names) - Tools (Telegraf, Chronograf, Kapacitor, Flux, Explorer) display questions without version hints - Pre-fills chat input with [version: /path/] for InfluxDB database products - Users can easily edit or remove the pre-filled text - Works for manual opens (Cmd+K) and programmatic opens - Converts module to TypeScript * refactor(ask-ai): change version format to 'My version: <product name>' Use human-readable product names instead of URL paths for better UX. Example: 'My version: InfluxDB 3 Core' instead of '[version: /influxdb3/core/]' * fix(ask-ai): restore working Kapa.open() pre-fill implementation - Replace textarea detection with direct Kapa.open() call - Add Kapa preinitialization code - Use click handler on .ask-ai-open button with capture phase - Handle conversation reset event to re-fill version context - Remove console logging for cleaner production code * fix(ask-ai): remove parentheses from example questions for consistency Make example question format match the pre-fill format: - Before: 'question (My version: product)' - After: 'question My version: product' This ensures users don't think there's a difference between the two formats. * fix(askai): add Explorer product mapping for Ask AI widget - Add influxdb3_explorer mapping to getCurrentProductData() - Add explorer context to getContext() function - Ensures Explorer pages use correct ai_sample_questions from products.yml - Reorder Explorer questions with 'install and run' first This fixes the issue where Explorer Ask AI widget was showing wrong example questions by properly loading the influxdb3_explorer config. * test(page-context): add comprehensive e2e tests for product mappings Add Cypress tests to validate page-context.js correctly identifies: - Product context values for all InfluxDB products - Product data from products.yml configuration - Version information - AI sample questions and source group IDs - Placeholder host values Tests cover: - InfluxDB 3 (Core, Enterprise, Explorer, Cloud variants, Clustered) - InfluxDB v2 and v1 - InfluxDB Cloud (TSM) - Tools (Telegraf, Chronograf, Kapacitor, Flux) Validates the fix for Explorer Ask AI showing correct example questions. Related to #jts-askai-group-filters branch work. * feat(test): add --no-mapping flag to e2e test runner Allow running functionality tests without requiring content file paths. The --no-mapping flag skips content-to-URL mapping, making it easier to run tests that don't depend on specific content files. Usage: # With content mapping (for content-specific tests) node run-e2e-specs.js content/influxdb3/core/_index.md # Without content mapping (for functionality tests) node run-e2e-specs.js --spec cypress/e2e/page-context.cy.js --no-mapping Benefits: - Simplifies running functionality tests like page-context.cy.js - Reduces test startup time by skipping unnecessary file mapping - Makes test commands clearer about their purpose The page-context test was updated to work correctly with this flag. * deps: update caniuse and related hook files * test: Add a `--no-mapping` flag to run tests without specific content files (i.e., test contains all the URLs it needs) * chore(ask-ai): Format example questions * test(page-context): add comprehensive e2e tests for all products in products.yml - Expanded test suite from 6 to 27 tests covering all products - Added tests for InfluxDB 3 products (Explorer, Core, Enterprise, Cloud Serverless, Cloud Dedicated, Clustered) - Added tests for InfluxDB v2 and Cloud (TSM) - Added tests for InfluxDB v1 and Enterprise v1 - Added tests for other products (Telegraf, Chronograf, Kapacitor, Flux) - Validates page mappings in page-context.js - Validates AI sample questions configuration in products.yml - All 27 tests passing * fix(page-context): correct enterprise_influxdb URL pattern matching - Changed pattern from /enterprise_v1/ to /enterprise_influxdb/ - Fixes Ask AI example questions not showing correctly for Enterprise v1 - Pattern now matches actual URL structure /enterprise_influxdb/v1/ - All 27 e2e tests passing * test(page-context): add UI validation for Ask AI widget configuration - Added 4 tests checking Kapa widget script data attributes - Tests verify data-modal-example-questions contains correct product-specific questions - Validates Explorer, Core, Enterprise, and Enterprise v1 configurations - All 31 tests passing (27 existing + 4 new UI tests) * feat(ask-ai): add help in Ask AI widget placeholder - InfluxDB placeholder recommends specifying product and version - Fix page-context.js to use products.influxdb_cloud instead of products.cloud - Add UI tests verifying version-specific naming in Kapa widget script tags * feat(ask-ai): Tailors placeholder for each version/product. Disables "Viewing <product>" in disclaimer note. |
||
|---|---|---|
| .. | ||
| influxctl | ||
| influxdb-client-libraries-reference | ||
| influxdb-v2 | ||
| influxdb3 | ||
| influxdb3-admin | ||
| influxdb3-api-reference | ||
| influxdb3-cli | ||
| influxdb3-get-started | ||
| influxdb3-internals | ||
| influxdb3-internals-reference | ||
| influxdb3-plugins | ||
| influxdb3-query-guides | ||
| influxdb3-reference | ||
| influxdb3-sample-data | ||
| influxdb3-visualize | ||
| influxdb3-write-guides | ||
| influxql-v3-reference | ||
| sql-reference | ||
| v3-core-enterprise-release-notes | ||
| v3-distributed-admin-custom-partitions | ||
| v3-distributed-internals-reference | ||
| v3-process-data/visualize | ||
| README.md | ||
| _index.md | ||
| identify-version.md | ||
| v3-line-protocol.md | ||
README.md
Shared content
This section is for content shared across multiple products and versions.
The /shared/_index.md frontmatter marks the /shared directory (/content/shared) and its
children as draft so they don't get rendered independently when the site is built.
The content of each shared document is included and rendered in pages that reference the
file as a source in their frontmatter.
Use shared content
-
Create a new folder for the content in the
/content/shared/directory. -
Copy the markdown files into the new folder.
-
Remove any frontmatter from the markdown files in the shared directory. If the first line starts with a shortcode, add an HTML comment before the first line, otherwise Hugo will err.
-
In each of the files that use the shared content, add a source to the frontmatter that points to the shared markdown file—for example:
source: /shared/influxql-v3-reference/regular-expressions.md -
In the doc body, remove the shared Markdown text and add a comment that points to the shared file, in case someone happens upon the page in the repo--for example, in
/content/influxdb3/core/reference/influxql/regular-expressions.md, add the following:
//SOURCE is a comment anchor (recognized by the Comment Anchors editor extension)
to make the file path clickable.