### **PR Type** Enhancement, Bug fix ___ ### **Description** - Add custom value support in variable selectors - Preserve custom entries when filtering multi-select - Remove deprecated URL initial value logic - Standardize popup behavior and label casing ___ ### **Changes walkthrough** 📝 <table><thead><tr><th></th><th align="left">Relevant files</th></tr></thead><tbody><tr><td><strong>Enhancement</strong></td><td><table> <tr> <td> <details> <summary><strong>VariablesValueSelector.vue</strong><dd><code>Custom value filtering in VariablesValueSelector</code> </dd></summary> <hr> web/src/components/dashboards/VariablesValueSelector.vue <li>Comment out URL-based initial value handling<br> <li> Merge custom typed values into filtered selections<br> <li> Adjust multi-select filter to include custom entries<br> <li> Minor formatting refactor for SQL query call </details> </td> <td><a href="https://github.com/openobserve/openobserve/pull/7341/files#diff-5c6e3bcb87cb64f25bf8157a541604b7a4904c1282acf662cab5d76a5be6bd56">+36/-26</a> </td> </tr> <tr> <td> <details> <summary><strong>VariableQueryValueSelector.vue</strong><dd><code>Custom value support in VariableQueryValueSelector</code> </dd></summary> <hr> web/src/components/dashboards/settings/VariableQueryValueSelector.vue <li>Always show custom value option when typing<br> <li> Append <code>::CUSTOM_VALUE</code> to custom selections<br> <li> Update <code>filteredOptions</code> and <code>displayValue</code> to label customs<br> <li> Remove <code>SELECT_ALL_VALUE</code> and customs on regular select<br> <li> Close popup after custom or regular value selection </details> </td> <td><a href="https://github.com/openobserve/openobserve/pull/7341/files#diff-2cca760c14e835bd1845485fb5517a60f71a6dc23626a6381c8559b82476f5f4">+62/-20</a> </td> </tr> </table></td></tr><tr><td><strong>Configuration changes</strong></td><td><table> <tr> <td> <details> <summary><strong>constants.ts</strong><dd><code>Add CUSTOM_VALUE constant</code> </dd></summary> <hr> web/src/utils/dashboard/constants.ts <li>Add <code>CUSTOM_VALUE</code> constant for custom entries<br> <li> Keep <code>SELECT_ALL_VALUE</code> export unchanged </details> </td> <td><a href="https://github.com/openobserve/openobserve/pull/7341/files#diff-a5e1b14a291a4b42368faa0160f555b19bdc1a542624d4f89ea6e3ed7c4a664d">+2/-1</a> </td> </tr> </table></td></tr></tr></tbody></table> ___ > <details> <summary> Need help?</summary><li>Type <code>/help how to ...</code> in the comments thread for any questions about PR-Agent usage.</li><li>Check out the <a href="https://qodo-merge-docs.qodo.ai/usage-guide/">documentation</a> for more information.</li></details>
web
This template should help get you started developing with Vue 3 in Vite.
Recommended IDE Setup
VSCode + Volar (and disable Vetur) + TypeScript Vue Plugin (Volar).
Type Support for .vue Imports in TS
TypeScript cannot handle type information for .vue imports by default, so we replace the tsc CLI with vue-tsc for type checking. In editors, we need TypeScript Vue Plugin (Volar) to make the TypeScript language service aware of .vue types.
If the standalone TypeScript plugin doesn't feel fast enough to you, Volar has also implemented a Take Over Mode that is more performant. You can enable it by the following steps:
- Disable the built-in TypeScript Extension
- Run
Extensions: Show Built-in Extensionsfrom VSCode's command palette - Find
TypeScript and JavaScript Language Features, right click and selectDisable (Workspace)
- Run
- Reload the VSCode window by running
Developer: Reload Windowfrom the command palette.
Customize configuration
See Vite Configuration Reference.
Project Setup
npm install
Compile and Hot-Reload for Development
For stand-alone UI development environment, create .env file and which contains below environment variable
VITE_OPENOBSERVE_ENDPOINT=http://localhost:5080/
npm run dev
Type-Check, Compile and Minify for Production
npm run build
Run Unit Tests with Vitest
npm run test:unit
Run End-to-End Tests with Cypress
npm run test:e2e:dev
This runs the end-to-end tests against the Vite development server. It is much faster than the production build.
But it's still recommended to test the production build with test:e2e before deploying (e.g. in CI environments):
npm run build
npm run test:e2e
Lint with ESLint
npm run lint