github ulsklyc/yuvomi v2.94.0

one hour ago

Changed

  • The budget and the subscriptions check every request against the published API
    description.
    This is about your own API clients; the app sends nothing that is refused now.
    Under /api/v1/budget (accounts, categories, entries, series, loans, plans, statistics,
    transfers) and /api/v1/budget/subscriptions, input that used to be quietly accepted,
    replaced or answered with a 500 is now refused with a 400:

    • a path id that is not plain digits: 1abc, 1.0 and 1e0 reached account, entry or loan 1,
      0x1 and 1.0 reached transfer or subscription 1 - also to delete it, and POST /subscriptions/0x1/renew booked a payment;
    • a month outside 01 to 12: GET /budget?month=2026-13 with a running series wrote an entry
      dated 2026-13-05, a loan stored start_month: "2026-13", and the summary, the plan and
      the export answered for month 13; a day that is not YYYY-MM-DD (anchor=2026-13-45 of the
      statistics answered 500);
    • a number, list, object or truth value in a text field: an account, category, entry,
      transfer, loan or subscription category named {} was stored as "[object Object]", a
      number as text; on editing an entry, a series, a loan or a subscription a number answered
      500;
    • null, an empty string, text, a truth value or a list as an amount: null and "" set an
      entry, a series, an account's starting balance or the subscription budget to 0, true
      counted as 1, [5] as 5, "0x10" as 16; credit_limit: "" is now null to clear it;
    • an unknown interest_mode of a new loan became a loan without interest, an unknown
      visibility of an entry, transfer, loan or subscription the default; an unknown loan
      direction or account type ("" was stored as the type), category type,
      recurrence_interval (null answered 500), billing_cycle (missing or "" answered
      500) or end_type;
    • switches that are not true/false (0/1 on entries): is_recurring: "false" started
      a series, archived: "false" archived an account;
    • ids in a body that are not whole numbers: account_id: "" or "1", a subscription's
      category_id: true (a 500), responsible_user_ids and attachment_document_ids with
      non-numbers (dropped silently), the order lists (order: [{}] of the categories answered
      500, missing or empty changed nothing; the subscription order took any list);
    • a query of the logo search that is not text (5 was looked up as the website 5);
    • a query value outside its type, or given twice: scope=x, account_id=abc, loan_id=abc,
      a month of the export or plan that is not YYYY-MM (the current month), range=day,
      include_archived=yes, a subscription status, enabled, category_id or
      payment_method_id outside its values (no filter, or an empty list).

    The check runs before the row is looked up, so a bad request is a 400, not a 404 or 403 (the
    write rule of the personal budget mode); a valid one meets those as before. Lengths, ranges,
    the calendar day and every refusal with a reason the budget page shows stay with the routes;
    a body of the wrong type now answers reason: validation with the field (for example
    entry_date_invalid for date: "nope", loan_direction_invalid for an unknown direction).
    The loan preview answers an unknown interest_mode with 400 instead of { ok: false }. A
    PUT without a body is a 400; PATCH /budget/{id}/confirm still takes none. An unexpected
    error of a subscription route now answers Internal server error. like every other route
    (it was Internal error.).

  • The shopping list, documents, the document storage settings and the DMS connection check
    every request against the published API description.
    This is about your own API clients;
    the app sends nothing that is refused now (from this release on it sends the folder of a
    document, the DMS account and the order of the shopping categories as numbers). Under
    /api/v1/shopping and /api/v1/documents (with storage/google-drive and dms), input that
    used to be quietly accepted, replaced or answered with a 500 is now refused with a 400:

    • a path id that is not plain digits: 0x1, 1.0 and 1e0 reached document 1, and on the
      shopping list 1.0 reached list or item 1;
    • a number, list, object or truth value in a text field: a shopping list, shop, category,
      folder or document named {} was stored as "[object Object]", a number as text;
    • an unknown visibility of a new or linked document became family, visible to the whole
      household; an unknown category became other, and on editing a document an unknown
      visibility, category or status was ignored;
    • an unknown DMS provider became paperless; a dms_document_id that is neither text nor a
      number was stored as its text (true, "[object Object]");
    • an unknown folder_key of an upload was dropped; an unknown selected_upload_backend, an
      enabled of the WebDAV settings that is not true or false;
    • a number field sent as a truth value, text or list: expiry_reminder_days: true was stored
      as 1, price_cents: true, [] and "0x10" as 1, 0 and 16; ids in a body that are not
      whole numbers or digit text (folder_id, parent_id, subject_user_id, account_id,
      document_id; parent_id: true and "0x1" were read as folder 1);
    • archived: "false" and 0 archived a document; preview: "true" of the meal-plan import
      ran the real import; is_checked other than true, false, 0 or 1;
    • order of the shopping categories that is not a list of ids ([{}] and [true] answered
      500, [1.5] and ["x"] changed nothing), items of the pantry import that is not a list
      of entries (taken as empty), ids of the kitchen undo that are not whole numbers (dropped);
    • a query value outside its type, or given twice: a doubled q of the shopping suggestions
      answered 500; status, category, folder_id and expiring of the document list and an
      empty documents of a folder deletion fell back silently to no filter or unfile;
      limit of the price history outside 1 to 50 was clamped.

    The check runs before the row is looked up, so a bad request is a 400, not a 404, 403 or 409;
    a valid one meets those as before. The admin check of the storage settings, Google Drive and
    every DMS route, and the meal-plan and pantry rights of the two kitchen imports come first:
    403 stays 403, also for a bad request. Lengths stay with the routes. Sharing a document with
    an id that has no account answers the 400 of a non-member instead of 500. A DMS account stored
    with a built-in property name as its provider no longer reaches a broken adapter.

  • Contacts, contact sync and the meal plan check every request against the published API
    description.
    This is about your own API clients; the app sends nothing that is refused now
    (from this release on the meal dialog sends the chosen recipe as a number). Under
    /api/v1/contacts, /api/v1/contacts/cardav and /api/v1/meals, input that used to be
    quietly accepted, replaced or answered with a 500 is now refused with a 400:

    • a path id that is not plain digits: 0x10 and abc found nothing (404), 1e2 reached row 1;
    • a number, list, object or truth value in a text field: a contact named {} was stored as
      "[object Object]", a number as text; on editing a contact or a meal, and on the
      ingredients of a meal, a number answered 500;
    • recipe_id and cook_user_id that are neither whole numbers nor digit text ("0x10" was
      read as recipe 16, true as 1 or a 500), a listId of a transfer that is not a whole
      number, a meal type that is empty or null, a series end that is not a day;
    • ingredients and assignments that are not lists of objects (500);
    • an unknown scope on PUT and DELETE /meals/{id}: on DELETE it deleted the meal;
    • week of the meal plan that is not a day: abc and an empty value fell back to the current
      week, 2026-13-45 answered 500, 2026-02-30 rolled over into March;
    • order of the contact categories that is not a list of text (taken as empty, or 500 for an
      object entry), a category edit with neither name nor color;
    • CardDAV: account fields that are not text (a password that was not text counted as empty),
      enabled of an address book that is not true or false; the refusal carries
      reason: "validation" and no errorCode, and the contact sync page says its sentence for
      it;
    • queries given twice (a doubled q of the meal suggestions answered 500).

    The check runs before the row is looked up, so a bad request is a 400, not a 404, 403 or 409;
    a valid one meets those as before. The admin check of contact sync and the shopping write
    right of the two transfers to the shopping list come first: 403 stays 403, also for a bad
    request. Lengths stay with the routes, with their reason and params.limit. Deleting a
    contact sync account that does not exist answers 404 (account_not_found) instead of 500. A
    week start stored as a built-in property name (constructor) no longer breaks the meal plan.

  • The shops and the price history of the shopping list answer an unexpected failure with the
    same sentence as the rest of the API.
    GET, POST, PUT and DELETE under
    /api/v1/shopping/stores and GET /api/v1/shopping/price-history said "Internal error" on
    a server-side failure; they now say "Internal server error." like every other module. Status
    500 and code are unchanged, and so is every answer that names a known cause.

  • Health answers an unexpected failure with the same sentence as the rest of the API.
    Vitals, medications and the dose log, lab reports, activities, the CSV exports, the cycle
    tab, caregivers, preventive care and nutrition under /api/v1/health said
    "Internal error." on a server-side failure; they now say "Internal server error." like
    every other module. Status 500 and code are unchanged. Every answer that names a known
    cause stays as it was: the fasting refusals with their reason (and the current record of
    a conflict), an undo of a dose that is not recorded (health_dose_pending), the reasons of
    the cycle import, the vital limits and units, and the refusals of care. The cycle feed,
    fasting and the visibility defaults answered this way already.

  • Health checks every request against the published API description. This is about your
    own API clients; the app sends nothing that is refused now (from this release on it sends the
    type of a preventive-care record as a number). Under /api/v1/health, input that used to be
    quietly accepted, replaced or answered later is now refused with a 400:

    • a path id that is not plain digits: 7abc, 1e2, 1.5 and " 5" reached row 7, 1, 1 and
      5, and on fasting records 0x10 reached record 16;
    • a number sent as text, a truth value or a list in a number field: "0x10", " ", [] and
      true were stored as 16, 0, 0 and 1 (vital values, stock and doses, lab values, activity
      numbers, nutrients, cycle settings);
    • an unknown value where the module has a list: visibility, dose status, lab flag, cycle flow
      and the day log choices, basal temperature unit, contraception, preventive-care kind, meal
      type, the areas of the visibility defaults; active and prn of a new medication or
      schedule that are not true/false/1/0 became the default;
    • a number, list or object in a text field (stored as text, {} as "[object Object]"), ids
      in a body that are neither whole numbers nor digit text (user_id, schedule_id,
      type_id, notify_partner_user_id), symptoms that is neither a list nor text (it cleared
      the day's symptoms) and results of a lab report that is not a list (dropped);
    • caregiver_ids with an entry that is not an id: ["abc"] WITHDREW ALL CARE for the person;
    • PATCH /health/fasting/{id} with visibility: null, which made a shared fast private;
      fasting goal_minutes, rating and expected_revision sent as text;
    • queries: user_id that is not plain digits or 0 (read as "everybody visible"), active
      other than 1, 0, true, false, export dates that are not a day (ignored), an unknown
      meal_type, and any parameter given twice;
    • a missing body on the routes that read one; {} sent on purpose still passes where the
      route took it before. POST /health/logs/{id}/skip reads no body.

    The check runs before the row is looked up, so a bad request is a 400, not a 404 or 409; a
    valid one meets those as before. The fasting capability and the admin check of caregivers and
    preventive-care types come first: 403 stays 403, also for a bad request. Rules the
    description cannot carry stay with the routes: vital limits and units, the order of start and
    end, the CSV import rows, revisions and overlaps of fasts. A basal temperature unit named like
    a built-in property (constructor) no longer passes the range check.

  • Editing a shared expense takes the whole expense. This is about your own API clients; the
    app sends every field now. PUT /split-expenses/expenses/{id} without description,
    currency, converted_amount, converted_currency, exchange_snapshot, split_method or
    expense_date cleared the stored note and exchange snapshot, read the amount in the converted
    currency, set the converted amount and currency back to the amount and currency, split the
    amount equally and moved the expense to today. All seven are required now besides title and
    amount; null still clears the note and the snapshot and stands for the amount, and
    expense_date: "" is still today. payer_id, participants, category, budget_category
    and attachment_document_ids stay optional and keep the stored value when left out. The edit
    dialog no longer drops the stored conversion and exchange snapshot of an expense whose amount
    and currency it leaves unchanged, and the exact shares of such a converted expense are entered
    and checked in the converted currency, as the server adds them up.

  • Saving the cycle settings takes all of them. This is about your own API clients; the app
    sends every field already. PUT /health/cycle/settings without one of its fields reset it to
    its default: the cycle and period lengths, the due date, contraception, the period reminder
    and the partner notification were cleared, the luteal phase went back to 14 days, fertility
    tracking and the PMS window were switched on, pregnancy and perimenopause mode and the daily
    log nudge were switched off and the default visibility became private ({} reset them all).
    All 14 fields are required now; null still clears a value where the field takes it, and
    luteal_length: null is still 14.

  • Saving a cycle day again takes the whole day. This is about your own API clients; the app
    sends the whole day already. POST /health/cycle/logs on a day that has a log without flow,
    note, visibility, symptoms, basal_temp, basal_temp_unit, cervix_mucus, lh_test,
    pregnancy_test or intimacy cleared the stored value, emptied the symptoms and made the day
    private. These ten are required now besides log_date; null and "" still mean "not
    given". feelings and mood stay optional and keep the stored feelings when both are left
    out.

  • Setting a nutrition target takes all eight nutrients. This is about your own API clients;
    the app sends all eight already. PUT /health/nutrition/targets without a nutrient unset it,
    and {} deleted the whole target. All eight are required now; null unsets one, and eight
    null still delete the target. user_id stays optional and means the caller when left out.

  • Recording a dose takes its status. This is about your own API clients; the app sends it
    already. POST /health/medications/{id}/logs without status stored pending, and repeating
    a planned dose that was taken (same schedule_id and scheduled_at) reset it to pending
    and dropped its time. status is required now; null still means pending. taken_at,
    dose_qty, note and stock_deduct stay optional: left out, a repeat keeps the stored time,
    dose and note and deducts nothing.

  • Renaming a contact takes all five name parts. This is about your own API clients.
    PUT /contacts/{id} with some of firstName, lastName, middleName, namePrefix and
    nameSuffix cleared the ones left out, so a middle name, title or suffix from a vCard or
    CardDAV was lost. Sent together they are required together now: one without the others is a
    400 naming a missing part; null still clears a part, and leaving out all five keeps them.

  • Editing a document takes its access list. This is about your own API clients; the app
    sends it already. PUT /documents/{id} without allowed_member_ids emptied the list, so a
    restricted document silently lost every member it was shared with. allowed_member_ids is
    required now ([] shares it with nobody); for family and private it is ignored as before.
    Every other field stays optional and keeps the stored value when left out.

  • An exchange snapshot is an object or null. This is about your own API clients: on
    POST /split-expenses/groups/{id}/expenses and PUT /split-expenses/expenses/{id},
    exchange_snapshot sent as false, 0, "" or any other value that is not an object is now
    refused with a 400, where false, 0 and "" were stored as no snapshot and other values as
    sent.

  • Backup answers an unexpected failure with the same sentence as the rest of the API.
    GET /api/v1/backup/database said "Database backup failed.", POST /api/v1/backup/trigger
    "Backup trigger failed." and PUT /api/v1/backup/webdav/config "Failed to save WebDAV config." on a server-side failure; they now say "Internal server error." like every other
    module. Status 500 and code are unchanged. Every answer that names a known cause stays as it
    was: a download whose backup failed its integrity check (backup_verify_failed), a local
    failure of the WebDAV upload (backup_local_failed), the 502 of the WebDAV server, the
    errorCode of the WebDAV settings and the reasons of a restore. Shared expenses answered
    this way already.

  • Shared expenses, backup and the system diagnostics check every request against the
    published API description.
    This is about your own API clients; the app sends nothing that
    is refused now (from this release on it sends the payer and payee as numbers). Under
    /api/v1/split-expenses, /api/v1/backup, /api/v1/system and /api/v1/changelog, input
    that used to be quietly accepted, replaced or answered later is now refused with a 400:

    • a path id that is not plain digits: 0x10, 1e1 and " 5" read group, expense or
      recurring expense 16, 10 and 5, and 7abc or 1.5 were a 404;
    • an unknown value where the module has a list: group type, default_currency,
      default_split_method, an expense or settlement currency and converted_currency,
      split_method, category, a recurring frequency, a member role, a guest
      family_role, and the filters status (groups) and category (expenses). They were
      replaced with a default (general, equal, the group currency, guest, other) or
      ignored;
    • a number, truth value, list or object in a text field (a guest password: {} was stored as
      "[object Object]"), an amount sent as a number, and ids in a body that are neither whole
      numbers nor digit text (payer_id, payee_id, participants, splits[].user_id,
      user_id, contact_id, proof_document_id, attachment_document_ids);
    • attachment_document_ids that is not a list on PUT /split-expenses/expenses/{id}:
      null, a single id or text REMOVED EVERY RECEIPT of the expense. Leave the field out to
      keep them, send [] to remove them;
    • PUT /backup/webdav/config with a username, password or remotePath that is not text
      (username: 5 was a 500) or a keep that is not a whole number (7.5 was stored as 7);
    • queries: limit, offset and before_id that are not plain digits, recurring other than
      1, and any parameter given twice. limit above 100 and a negative offset are still
      capped, as described;
    • a missing body on the routes that read one; {} sent on purpose still passes where the
      route took it before (PATCH /split-expenses/groups/{id}).

    What stays allowed is in the description now too: null or "" for "no value" where the
    routes read it so, digit text for ids (the legacy form), unknown fields, no body at the pause
    toggle. Rules the description cannot carry stay with the routes and their sentences: an empty
    name after trimming, amounts and their decimal places, the sums of a split, membership,
    budget categories (unknown_budget_category), the WebDAV address pattern and password rule
    (errorCode). missed keeps its reason invalid_missed. The check runs before the group,
    expense or recurring expense is looked up, so a bad request is a 400, not a 404, 403 or 409;
    a valid one meets those as before. The admin check of backup and diagnostics and the refusal
    of a shared-expense guest creating a group come first: 403 stays 403, also for a bad request.
    Text lengths count the value as sent.

  • Replacing a moved or skipped waste pickup or a day of the shift schedule takes the whole
    entry.
    This is about your own API clients; the app sends every field already. A PUT
    replaces what is stored, so a field left out no longer stands for a value:

    • PUT /waste/schedules/{id}/overrides/{originalDate} without replacement_date and note:
      an empty body skipped the pickup, and a missing note wiped the stored one. Both are required
      now; replacement_date: null skips the pickup;
    • PUT /schedule/overrides/{dateKey} without shift_type_id, note and field_values: a
      missing shift type made the day free, a missing note wiped the stored one, and missing field
      values kept the stored ones while everything else was replaced. All three are required now;
      shift_type_id: null is the free day, and field_values: {} clears the values. user_id
      stays optional and defaults to you.
  • Waste collection and the shift schedule answer an unexpected failure with the same sentence
    as the rest of the API.
    The routes under /api/v1/waste (types, schedules and their
    overrides, one-off pickups, occurrences, import sources, file import, reminder settings) said
    "Internal error" on a server-side failure, DELETE /api/v1/schedule/shift-types/{id} said
    "Internal error." and GET /api/v1/schedule/entries said "Schedule entries could not be resolved."; they now say "Internal server error." like every other module. Status 500 and
    code are unchanged. Every answer that names a known cause stays as it was: a refused input,
    a missing record or a conflict of waste collection, the 502 of a subscribed address without
    calendar entries, and the 409 of a shift type still in use. The waste feed, the schedule feed
    and the own schedule settings answered this way already.

Fixed

  • Saving a contact in the app keeps its middle name, title and suffix. A contact imported
    from a vCard or synced over CardDAV lost them the first time its form was saved, because the
    form sent only the first and last name; it now sends the stored ones along.
  • A shared expense converted into a currency with other decimal places reports the converted
    amount correctly.
    converted_amount in the expense answers was written with the decimal
    places of currency instead of converted_currency: 1500 JPY converted from USD read
    "15.00", and sending it back was refused. converted_amount_minor was always right.
  • Exact shares of an expense converted into COP, HUF, IDR or IRR can be saved again. The
    converted amount keeps two decimal places (for example 3581.47 HUF), but the share fields
    allowed none for these currencies, so the shares could never add up to it. They now accept
    the decimal places the converted amount is stored with.
  • The running total under exact shares of such an expense shows the stored decimal places.
    It showed 3,581 HUF while the shares had to add up to 3,581.47 HUF; it now shows 3,581.47 HUF.
  • A shared expense saved without an exchange rate answers exchange_snapshot: null. Creating
    or replacing an expense without a rate stored the text "null", and the expense answers
    returned "exchange_snapshot": "null" for it. New and replaced expenses now store no value and
    answer null; expenses saved before keep "null" until they are saved again.

Don't miss a new yuvomi release

NewReleases is sending notifications on new releases.