@valbuild/core 0.111.0 → 0.117.0

package/CHANGELOG.md

@@ -0,0 +1,56 @@
+# @valbuild/core
+
+## 0.117.0
+
+### Patch Changes
+
+- [#581](https://github.com/valbuild/val/pull/581) [`d94a40f`](https://github.com/valbuild/val/commit/d94a40f8bd11027636d183e293aced820b6f341f) Thanks [@freekh](https://github.com/freekh)! - Images no longer show a validation warning in the editor when nothing is wrong
+  with them.
+
+  Every `s.image()` carrying width, height or a mime type used to be marked in VS
+  Code with "Found image metadata, but it could not be validated", whether or not
+  the metadata was correct — so the warning sat on every image in the project and
+  never went away, not even after applying its own quick fix.
+
+  That message was never a finding. `@valbuild/core` cannot read files, so it
+  cannot answer whether stored dimensions match the image, and it hands the
+  question on as an `image:check-metadata` fix instead. `val validate` has always
+  resolved that by reading the file and comparing; the language server now does
+  the same, and reports only what actually disagrees:
+
+  ```
+  Image width is incorrect! Found: 800. Expected: 944
+  ```
+
+  An image whose metadata is right gets nothing. A missing `width`, `height` or
+  `mimeType` is reported, as is a stale one, with the quick fix still offered. A
+  file that is not on disk is still reported as a missing file rather than as a
+  metadata problem.
+
+  The four messages involved say what they mean now, in the editor and in
+  `val validate` alike:
+
+  - "Image metadata has not been checked against the file." (was "Found image
+    metadata, but it could not be validated. An image must have a width (positive
+    number), a height (positive number) and a mime type." — which described a
+    check that never ran)
+  - "Image metadata is missing: width, height and mimeType." (was "Could not
+    validate Image metadata.")
+  - "File mimeType has not been checked against the file." (was "Found mimeType,
+    but it could not be validated.")
+  - "File metadata is missing: mimeType." (was "Missing File mimeType.")
+
+  Also fixes an `s.file()` whose `mimeType` is missing: it reported "Mime type and
+  file extension not matching. Mime type is 'undefined'" with no fix attached, so
+  no quick fix was offered and the `file:add-metadata` case was unreachable. It
+  now reports the missing mime type and offers to add it.
+
+- [#579](https://github.com/valbuild/val/pull/579) [`b2812ae`](https://github.com/valbuild/val/commit/b2812ae4ee03e005ecead3365f49c625e536f94d) Thanks [@freekh](https://github.com/freekh)! - Every release now ships a changelog. Each package's `CHANGELOG.md` records what
+  changed under the version that shipped it — with a link to the pull request, the
+  commit and the author — and the same entry becomes the body of the GitHub
+  Release for the tag. The file is included in the npm tarball, so it is also
+  readable from an installed copy.
+
+  Up to now those changelogs were generated empty, and the GitHub Releases with
+  them, so there was no record of what any given version contained. Releases from
+  this one on have one; earlier versions stay blank.

package/dist/declarations/src/index.d.ts

@@ -31,7 +31,7 @@ import { ModulePath, SourcePath, getValPath, isVal } from "./val/index.js";
 import { createValPathOfItem } from "./selector/SelectorProxy.js";
 import { Operation } from "./patch/index.js";
 import { initSchema } from "./initSchema.js";
-import { getMimeType, mimeTypeToFileExt, filenameToMimeType } from "./mimeType/index.js";
+import { getMimeType, mimeTypeToFileExt, filenameToMimeType, mimeTypeMatchesAccept } from "./mimeType/index.js";
 import { type ImageMetadata } from "./schema/image.js";
 import { type FileMetadata } from "./schema/file.js";
 import { isJson, getJsonImport, resolveJsonValues } from "./source/json.js";
@@ -114,6 +114,7 @@ declare const Internal: {
     getMimeType: typeof getMimeType;
     mimeTypeToFileExt: typeof mimeTypeToFileExt;
     filenameToMimeType: typeof filenameToMimeType;
+    mimeTypeMatchesAccept: typeof mimeTypeMatchesAccept;
     EXT_TO_MIME_TYPES: Record<string, string>;
     MIME_TYPES_TO_EXT: {
         [k: string]: string;

package/dist/declarations/src/mimeType/convertMimeType.d.ts

@@ -1,3 +1,17 @@
 export declare function getMimeType(base64Url: string): string | undefined;
 export declare function mimeTypeToFileExt(mimeType: string): string;
 export declare function filenameToMimeType(filename: string): string | undefined;
+/**
+ * Whether `mimeType` satisfies an `accept` string.
+ *
+ * `accept` is the HTML file-input syntax: a comma-separated list of exact mime
+ * types (`image/png`), type wildcards (`image` followed by `/` and a star) or
+ * the catch-all star-slash-star.
+ *
+ * This lived in three places - `ImageSchema`, `FileSchema` and the media
+ * branch of `RecordSchema` - which is how the third copy grew a redundant
+ * `image` wildcard case that the general wildcard branch already covered.
+ * Anything that has to decide whether an `accept` is satisfied, validation and
+ * editor tooling alike, should call this.
+ */
+export declare function mimeTypeMatchesAccept(mimeType: string, accept: string): boolean;