-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Detailed list doesn't work with docs:preview (only works with docs:dev) #2485
Comments
Somehow vitepress/src/client/theme-default/components/VPLocalSearchBox.vue Lines 161 to 162 in d62e6f6
|
I think we can fix this, but there is a change required at your side too. Your csv file paths need slight refactoring: (Example, usage in other files also needs to be updated.) - d3.csv("../data/aapl.csv", d3.autoType).then((data) => (aapl.value = data));
- d3.csv("../data/goog.csv", d3.autoType).then((data) => (goog.value = data));
- d3.csv("../data/sf-temperatures.csv", d3.autoType).then((data) => (sftemp.value = data));
+ d3.csv(withBase("/data/aapl.csv"), d3.autoType).then((data) => (aapl.value = data));
+ d3.csv(withBase("/data/goog.csv"), d3.autoType).then((data) => (goog.value = data));
+ d3.csv(withBase("/data/sf-temperatures.csv"), d3.autoType).then((data) => (sftemp.value = data));
|
fixed in 80e734d |
Describe the bug
Hello, thank you so much for vitepress — we are using it for https://observablehq.com/plot/
Currently we see that the instant search detailed list feature works in
docs:dev
but does not work withdocs:preview
(nor in production).We are currently using v1.0.0-alpha.72, but I tried locally upgrading to v1.0.0-beta.1 and the issue is still here.
Reproduction
Clone https://github.com/observablehq/plot
change vitepress version to v1.0.0-beta.1 in package.json
run yarn; yarn docs:build; yarn docs:preview
open the site and search “color”
screenshot: left: docs:dev; right: docs:preview
Expected behavior
The detailed list should appear.
System Info
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: