Add config field to disable opening in editor

[jemayn]

Hey Matt!

We are working on a site where the client needs to be able to see a list of orders made on the website in the backoffice. They shouldn't have the option of editing them, but need to be able to delete test / joke orders.

So I've created a listview that pulls the data from a custom repo and it all works just fine. I've added

.DisableCreate()
.DisableUpdate()

To the collection, however my issue is that they can still click the "name" property in the listview and then they enter an empty editor view (no editor is specified in my config).

I can't make it readonly as we still need the delete action.

So my idea is that it would be awesome if we could add a "DisableEditorView()" method or something along those lines? 🙂

[mattbrailsford]

Yea, that could work. I'm also trying to work out if we can say "if no Editor() config is called, could / should this disable and editor view anyway? I guess the only use where that might be a problem is if you have an entity that is just a "name" field as like you say, that's default 🤔

I guess initally I thought it would always be possible to view the full entry, as in your example, would they need to see the full order to decide it's test / joke order? In that case, you'd want to go to the editor view, but potentially have all the fields uneditable / save button disabled (which the DisableUpdate should trigger).

[jemayn]

The info we pass along is very limited, so they can always see it all in the listview which was why I didn't set up the editor.
I initially assumed that adding no editor view would disable it - I guess if someone needs the editor view with just the name field they could add an editor with no additional fields?