fcc5d99d40
* add vitest * initialize lib w/ tests * move to dev dep * run tests in CI * update file names * move api folder to lib * move api and api types to same folder * update generator outpath * rm husky * i guess i _did_ need those types * reorg types * extract validators into testable components * (WIP) start composable testing * fix import type * fix linter complaint * simplify icon type def * fix linter errors (maybe?) * rename client file for sorting
39 lines
859 B
TypeScript
39 lines
859 B
TypeScript
/**
|
|
* use-display-text module contains helpful utility functions to compute the display text when provided
|
|
* with the food, units, quantity, and notes.
|
|
*/
|
|
|
|
import { IngredientFood, IngredientUnit } from "~/lib/api/types/recipe";
|
|
|
|
export function getDisplayText(
|
|
notes = "",
|
|
quantity: number | null = null,
|
|
food: IngredientFood | null = null,
|
|
unit: IngredientUnit | null = null
|
|
): string {
|
|
// Fallback to note only if no food or unit is provided
|
|
if (food === null && unit === null) {
|
|
return `${quantity || ""} ${notes}`.trim();
|
|
}
|
|
|
|
// Otherwise build the display text
|
|
let displayText = "";
|
|
|
|
if (quantity) {
|
|
displayText += quantity;
|
|
}
|
|
|
|
if (unit) {
|
|
displayText += ` ${unit.name}`;
|
|
}
|
|
|
|
if (food) {
|
|
displayText += ` ${food.name}`;
|
|
}
|
|
|
|
if (notes) {
|
|
displayText += ` ${notes}`;
|
|
}
|
|
|
|
return displayText.trim();
|
|
}
|