Locode grid future

[diskman]

What is the future of grid implemented in locode? For example I am looking for below features

• inline edition
• presentation of hierarchical data (for example if there is self parent Id column it should be possible to collapse/expand partcular row)
• infinite scrolling
• checkbox selection/multiselection
• and many more (I am looking on doc https://mudblazor.com/components/table#default-table)

[mythz]

You can submit any feature requests to ServiceStack/Discuss Ideas · Discussions · GitHub with a lot more details on each feature request.

But a lot of these sounds like UX preferences which are unlikely to be considered unless there’s a lot of demand for it, e.g. I’ve no desire to over complicate it with a different way to edit data, esp. as we need the full screen real estate to show contextual validation errors.

You can see examples of how related data is handled here, i.e. you can navigate to the related data table, it doesn’t show it inline:

One to many in UI

I think you’re asking about defining POCO References, it’s not really possible to add them to Database-first Locode Apps like Northwind (since you can’t code-gen a new List<Order> property for the non-existent Order type), but if you export the database models into C# types you can add the POCO Reference on Customers to the Orders table, e.g: public class Customer { //... [Reference] public List<Order> Orders { get; set; } } This is used a lot in https://talent.locode.dev like its J…

Why would you need to multi select rows? You can only choose a single row to edit at a time.

But honestly I don’t see much on that page which I consider a good fit for Locode which is a RAD tool which auto generates its UI driven by the metadata of your Services, we support some declarative customizations but it’s never going to have the level of customizations of a developer control like their Table grid which requires a lot of bespoke code for each of their examples. Locode doesn’t do bespoke code with hard coded columns, it needs to be auto driven.

[diskman]

all is clear @mythz, it seems that the locode solution is not suitable for more advanced oprations on the data list.