@algolia/wizard 0.73.0 → 0.74.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/dist/main.js +3 -2
  2. package/package.json +1 -1
package/dist/main.js CHANGED
@@ -2260,7 +2260,7 @@ async function ensureApplication(resumeAppId) {
2260
2260
  // package.json
2261
2261
  var package_default = {
2262
2262
  name: "@algolia/wizard",
2263
- version: "0.73.0",
2263
+ version: "0.74.0",
2264
2264
  description: "Magically implement Algolia functionality in your codebase",
2265
2265
  type: "module",
2266
2266
  engines: {
@@ -5516,6 +5516,7 @@ function searchInstructions(input) {
5516
5516
  "Style the search surfaces through the widget's class and CSS-variable overrides (or, when hand-built, the app's existing theme tokens): give the results panel and the element that actually draws the input's border and background \u2014 for a widget, the form or wrapper it renders around the bare input \u2014 non-transparent surfaces, keep that frame distinguishable from the background behind it in every supported theme, and never assume a light surface or reuse the surrounding page's colors unchanged inside the panel.",
5517
5517
  "The panel takes its width from the input by default, so a small input makes it unreadably narrow: give it `min-width: min(320px, calc(100vw - 2rem))` independent of the input, cap its maximum width to the viewport, and anchor it to the input edge it opens from so widening does not push it off-screen.",
5518
5518
  "Match the application styles closely, including light, dark, and high-contrast themes the project already supports.",
5519
+ "Before reporting, mount the component and fix any type-check or lint errors your changes cause. If a tool limit is reached or an error remains unresolved, keep the implementation, report status=success, and name the remaining issue in the summary so validation can drive the next pass. Report status=fail only when no search implementation can be written, with the concrete blocker as the reason.",
5519
5520
  "The summary should be extremely concise; do not mention manual testing steps."
5520
5521
  ];
5521
5522
  }
@@ -7841,7 +7842,7 @@ function delay(ms) {
7841
7842
  // package.json with { type: 'json' }
7842
7843
  var package_default2 = {
7843
7844
  name: "@algolia/wizard",
7844
- version: "0.73.0",
7845
+ version: "0.74.0",
7845
7846
  description: "Magically implement Algolia functionality in your codebase",
7846
7847
  type: "module",
7847
7848
  engines: {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@algolia/wizard",
3
- "version": "0.73.0",
3
+ "version": "0.74.0",
4
4
  "description": "Magically implement Algolia functionality in your codebase",
5
5
  "type": "module",
6
6
  "engines": {