Skip to content

Commit bd38c1e

Browse files
committed
fix more links
1 parent 68bebcf commit bd38c1e

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

MyApp/_pages/releases/v6_09.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -279,7 +279,7 @@ type MarkdownInputOptions = "bold" | "italics" | "link" | "image" | "blockquote"
279279
```
280280
281281
Just like other Input components it can also be annotated on Request DTO string properties to change which Input component it should use in
282-
[AutoForm components](https://servicestack.net/vue/gallery/autoform), where it can be further customized with tailwind classes on its
282+
[AutoForm components](/vue/autoform), where it can be further customized with tailwind classes on its
283283
containing Field and Textarea Input elements, e.g:
284284
285285
```csharp
@@ -353,8 +353,8 @@ The AutoForm components and rapid development workflow enabled by [Locode's Auto
353353
most optimal UX but you don't want to leave the high productivity of Auto UI and Auto Form components to go back to creating manual forms.
354354

355355
Which we found ourselves in when developing CreatorKit where we want users to be able to quickly develop custom Email Templates and UIs, but not have to
356-
put in the effort to get the great UX we're used to when creating emails. For example we could've used the default [LookupInput](https://servicestack.net/vue/gallery/autoform#edit-form)
357-
that's inferred and rendered for [Reference Fields](https://servicestack.net/vue/gallery/autoquerygrid#reference-fields), but that would require opening a modal form to search through
356+
put in the effort to get the great UX we're used to when creating emails. For example we could've used the default [LookupInput](/vue/autoform#edit-form)
357+
that's inferred and rendered for [Reference Fields](/vue/autoquerygrid#reference-fields), but that would require opening a modal form to search through
358358
existing contacts every time we wanted to send an email.
359359

360360
But gmail have already showed us it's much more user-friendly and quicker to provide a non-modal autocomplete dropdown that automatically searches

MyApp/_pages/vue/custom-inputs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ This allows us to continue to benefiting rapid development workflow enabled by t
1212
to deliver the most optimal UX when we need to.
1313

1414
CreatorKit's [Email Templates](https://servicestack.net/creatorkit/portal-messages) are a good example of this, which instead of utilizing the standard
15-
[LookupInput](https://servicestack.net/vue/gallery/autoform#edit-form) (inferred from [Reference Fields](/vue/autoquerygrid#reference-fields))
15+
[LookupInput](/vue/autoform#edit-form) (inferred from [Reference Fields](/vue/autoquerygrid#reference-fields))
1616
to open a modal to select a contact from a Contacts DataGrid it uses a custom `EmailInput` Component to provide an optimal, user-friendly UX that
1717
we've come to expect from popular Email clients like gmail to provide a non-modal autocomplete dropdown that automatically searches our contact list
1818
as we type.

0 commit comments

Comments
 (0)