Is possible to change the the editor for a textfield by code?

[AmadeuAntunes]

I would like to change the editor for a textfield before render it.

[jptissot]

You can in a migration file. What do you mean when you say "Before render it"?

[willnationsdev]

@AmadeuAntunes I might recommend that you create a shape template with a shape type name targeting the Edit display type of that type/part/field so that you can make it render a hidden input with your hardcoded value instead of a select dropdown. See the Templates documentation for examples of template names and how they match up with shape type to override specific types of content.

[AmadeuAntunes]

I tried this way:

and in template I used

this way I could change the html render, however it affect all fields use this,

1 - is there other way to communicate with field template render without use ViewData?

2 - is there any way specify the field I would like to change readonly (if I use more then one field with this template using the viewData will change it for all)?

[AmadeuAntunes]

I just solved this way, is there a better solution ?

[willnationsdev]

If you're concerned about the template conflicting with other fields of the same type, you can just give the field a specific name and then use that, I think. At least, that's what the Templates docs seem to indicate, in their examples where the [FieldName] is part of the template, like this:

[PartType]__[FieldName]
[ContentType]__[PartName]__[FieldName]
[PartType]__[FieldName]__[ShapeType]
[ContentType]__[PartName]__[FieldName]__[ShapeType]

But, now that I look at your code, it seems like you're trying to define a piece of Settings data that gets associated with each instance of the given field type. I guess I'm confused why you don't just try to create a Settings value similar to the TextFieldSettings. If you wanted a module to add a ReadOnly checkbox to the settings fro the text field, you could probably do that. So you'd end up with something along the lines of...

@{
    var readOnlySettings = Model.PartFieldDefinition.GetSettings<ReadOnlySettings>();
    var readOnlyAttribute = readOnlySettings.IsReadOnly ? "readonly " : "";
}
<input asp-for="Text" class="form-control content-preview-text" @readOnlyAttribute dir="...etc.">

In an example such as this, every instance of the field gets its own copy of the Settings object and the data gets merged as part of the PartFieldDefinition. The only thing you have to do is define the settings and implement DisplayDriver that handles the Display/Edit/Update logic for the Settings object and the .cshtml template that defines the rendering logic.

For examples on how to do this, I would look at the OrchardCore source code and how it defines and updates TextFieldSettings.

[Skrypt]

If you want a readonly TextField just create an editor for it.

If you look at the OrchardCore.ContentFields module you will see how we define these editors.
You basically just need to create a TextField-ReadOnly.Option.cshtml file so that this "shape template" be added to the list of editor options. And then you create a TextField.ReadOnly.Edit.cshtml file with your custom textfield html. No need for a special field setting to do that.

Put that inside a module that extends the OrchardCore.ContentFields module and it should work.