v1.8

v1.8.6

Improvements

• NavLink can now show a summary popover
• NavLink can now truncates text when maxLength: is provided

v1.8.5

Improvements

• New ActionSkipsEmptyModel option added to component descriptor
  • Now, when the model is null, undefined, or empty string, or empty array, a component skips its action if ActionSkipsEmptyModel option is set
• Remote action configuration now fail descriptor generation with the get-method-with-body error code when a body is specified for a GET method
• LocalAction composables can now accept mutableValidation and/or events to perform any validation or publish an event
• Message component;
  • Layout is improved for mobile screens
  • It was using slate in dark theme for secondary instead of zinc, fixed

Bugfixes

• unref incorrectly converts blobs into empty objects, fixed
• Action's fetch request, was sending body due to incorrect casing on Get method, fixed
  • RemoteAction.Method is now in uppercase by default to match ofetch expectation
• Multiple data containers were causing a paging context key conflict in descriptors, fixed

v1.8.4

Bugfixes

• The remote action and refresh token does not use bfetch, fixed
• Security requirement objects were empty for endpoints, fixed

v1.8.3

Improvements

• useRedirect now supports query
  • Also, support include and exclude options
• usePathBuilder now has a buildDetailed overload
• ListIsDataTableUxFeature now detects async methods when generating actions for data tables
• The file-based routing feature is set to true by default. A page under /pages is no longer required

Bugfixes

• Inconsistent enum casing between response values and enum data, fixed
• OpenAPI security definitions are not displayed on endpoints, fixed
• Inputs does not emit ready for optional inputs, fixed
• ContextData does not return target properties with null values, fixed
• DataTableDefaultsUxFeature's DataTable.Actions remote action configuration convention overridden by DefaultThemeFeature, fixed
  • Minor breaking change: Execution order of this remote action configuration has been increased by 10
• The global $fetch override conflicts with Nuxt's $fetch, fixed
  • Minor breaking change: The global $fetch is now exposed as bfetch. To migrate, replace $fetch usages with bfetch

    // old
    const result = await $fetch("...", { method: "GET" });
    
    // new
    const result = await bfetch("...", { method: "GET" });
    

v1.8.2

Bugfixes

• Multiple entities weren't loading in Postgresql due to parallel sql commands, fixed

v1.8.1

Improvements

• Baked's tailwind.css file added to exports

v1.8.0

tailwindcss Upgrade

- [ ] Update `@mouseless/baked` packages to the latest version
- [ ] Remove the `@nuxtjs/tailwindcss` package
  - Remove it from your dependencies
  - If you have any related configuration in `nuxt.config.ts`, it can also be removed
- [ ] Move your global style overrides from `.scss` files into `components.css`
  - Import Tailwind at the top of  `components.css`
  - Wrap all overrides in the `utilities` layer
  - Group overrides by component using uppercase section comments (MDN style)
  - All custom css should be their `.b-component-...` class
  - Update the CSS import in `nuxt.config.ts`
  - Add `@mouseless/baked/tailwind.css` reference to use baked breakpoints overrides
- [ ] Replace custom CSS with Tailwind utilities using `@apply` wherever possible
- [ ] Move theme variables to `theme.css`
  - Rename your existing variables file or create a new `theme.css`
  - Extract repeated calculated values into CSS variables
  - Expose reusable variables through Tailwind's `@theme` when appropriate
- [ ] Move all styles from component `<style>` blocks into `components.css`
- [ ] Review your styles after the migration
  - Since component styles are no longer scoped, some selectors may have different specificity
  - You may need to add tailwind's `!` modifier in a few places to preserve the expected behavior
- [ ] Remove the `sass` package
  - Remove any related configuration from `nuxt.config.ts`
  - Remove the package from your dependencies
- [ ] If you previously customized Tailwind breakpoints or `useBreakpoints`, migrate them accordingly
  - `useBreakpoints` can continue to be configured as before
  - Tailwind breakpoints must now be defined in `theme.css` using `@theme`

Improvements

• name field added to show cases where the parameter id and name differ in .kdl
• CommandPatternCodingStyleFeature convention classes now support filtering via _whereContext
• ComponentPath matcher performance improved
• AllowsMultiple and ThrowIfNotTarget extension helpers performance improved

Breaking Changes

• Tailwind CSS has been upgraded from v3 to v4
  • @nuxtjs/tailwindcss is no longer required
  • Tailwind screens must now be configured via @theme
  • PrimeVue layer order is now theme, base, primevue, utilities
  • Existing styles may require migration
    • Follow the Tailwind CSS upgrade guide above
• override.scss has been renamed to component.css
• Properties with AnyByXx are no longer marked as unique
• AllowsMultiple is no longer an extension method on Type and Attribute; use the extension property instead
• PubliclyInitializableAttribute renamed to CommandAttribute
• CommandPatternCodingStyleFeature conventions now filter by CommandAttribute and CommandMethodAttribute
• CommandAttribute assignment now applied only to types with exactly one eligible command method and now supports both transient and non-transient types except locatable transient types
• FirstBy and SingleBy are no longer removed from route parts , and By is now removed only when it appears at the end of a method name

Library Upgrades