nested model properties
See original GitHub issuemy model has a daterange
@reactive mutable struct Pages <: ReactiveModel
daterange::R{DateRange} = DateRange(today(), (today() + Day(3)))
emnd
how do I refer to a nested properties ( :daterange.start will not work of course)
cell([div(
class = "q-pa-md",
style = "max-width: 300px",
[textfield(
"",
:daterange.start,
...'
Issue Analytics
- State:
- Created a year ago
- Comments:14 (6 by maintainers)
Top Results From Across the Web
Use Nested Model Properties - Kendo UI Grid for jQuery
The following example demonstrates how to use nested model properties. The CRUD operations are not fully configured. Edit Preview Open In Dojo.
Read more >Nested properties - IBM
Nested properties. The value of many properties is a reference to another resource. If the value of a property is a reference to...
Read more >Nested model properties value null - asp.net core
I have below class which contains nested model property
Read more >Using Nested Models in SqlModelMapper (multi level ...
This attribute maps a property from the Master Model to the Nested Model. It specifies that when there is an insert or update...
Read more >Nested properties - HCL Product Documentation
The value of many properties is a reference to another resource. If the value of a property is a reference to a resource,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The date isn’t showing because
render
function forDateRange
renames fields tofrom
&to
: https://github.com/GenieFramework/StippleUI.jl/blob/231c7aca8cd8e03288f483477271b815c10186ec/src/DatePickers.jl#L135-L137When you define field name as
Symbol("daterange.from")
intextfield
call, the date is showed correctly.While it’s good to keep the same names in principle, I’m not sure here: 1/ Quasar does not always make the best naming decisions, and this is one example 2/ Stipple abstracts away and improves the Quasar API (where possible) making the API “julian” - many names don’t translate well to Julia 3/ Why do we even need to know how props are called in Quasar? This should be a standalone element with its own docs.