Skip to content

Commit a3dce68

Browse files
committed
docs: remove merge conflict markers from dynamic_view.md documentation
1 parent 68b18e1 commit a3dce68

File tree

1 file changed

+0
-5
lines changed

1 file changed

+0
-5
lines changed

website/docs/widgets/dynamic_view.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -403,7 +403,6 @@ You can access specific array elements in the targetPath:
403403

404404
1. Use `targetPath` to extract only the data you need from complex API responses
405405
2. For list data, always use the `itemTemplate` property to define how each item should be rendered
406-
<<<<<<< HEAD
407406
3. **Always provide an `emptyTemplate`** for list-based views to handle empty API responses gracefully
408407
4. Design empty states that are informative and actionable - include clear messaging and relevant actions like refresh buttons
409408
5. Keep templates modular and reusable when possible
@@ -412,14 +411,10 @@ You can access specific array elements in the targetPath:
412411
8. Provide custom `loaderWidget` and `errorWidget` for better user experience
413412
9. Use `resultTarget` when you need to reference the data with a specific name in your template
414413
10. Keep templates modular and reusable when possible
415-
> > > > > > > dev
416414

417415
## Limitations
418416

419417
- API endpoints must return JSON data
420418
- For very large datasets, consider pagination or limiting the number of items to avoid performance issues
421419
- Complex data transformations may require custom code outside of the template system
422-
<<<<<<< HEAD
423-
=======
424420
- Nested array access in placeholder syntax is limited to the formats shown in the examples
425-
> > > > > > > dev

0 commit comments

Comments
 (0)