Skip to content

Remove the introduction to using custom fields #142

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
svelik0v wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Remove the introduction to using custom fields #142

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion custom-fields/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Custom field

When in content editing mode, content editors can modify content properties and add content relations via dedicated fields in the UI. For example, **ShortText**, **LongText**, **Number**, **Classifications**, **RelatedData**, and so on. With the Admin App, you can replace one of the default fields when creating and editing items with a custom one. In addition, you can implement a custom visualization for each custom field you create. You do this by providing a custom implementation of the [**FieldsProvider**](http://admin-app-extensions-docs.sitefinity.site/interfaces/fieldsprovider.html) interface. For each field rendered in the UI, the [**overrideField**](http://admin-app-extensions-docs.sitefinity.site/interfaces/fieldsprovider.html#overridefield) method is called. You can also provide a custom field registration for all of the fields or for a specific one.
With the Admin App, you can replace one of the default fields when creating and editing items with a custom one. The custom one builds upon FieldBase component which is the base component of of type of fields. You cannot build upon other type of fields e.g. DateField, RelatedData field, etc... . In addition, you can implement a custom visualization for each custom field you create. You do this by providing a custom implementation of the [**FieldsProvider**](http://admin-app-extensions-docs.sitefinity.site/interfaces/fieldsprovider.html) interface. For each field rendered in the UI, the [**overrideField**](http://admin-app-extensions-docs.sitefinity.site/interfaces/fieldsprovider.html#overridefield) method is called. You can also provide a custom field registration for all of the fields or for a specific one.
You also need to provide an implementation of the field for both read and write actions because there may be a case when due to lack of proper permissions or because the item is locked, it cannot be edited.

**NOTE:** Since these components are dynamically instantiated, you need to register them with the **entryComponents** property of the **NgModule**.
Expand Down