You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a requirement for hasOne in addition to hasMany and belongsTo
Currently hasOne is not part of our Q1 roadmap. So I have 2 questions:
@elv1s, what is the timeline you're thinking in terms of having hasOne support?
@strongloop/sq-lb-apex @raymondfeng@bajtos, after we have the 2 model relations, do you think it's a relatively small effort for us to get hasOne in?
EDIT: I realized that we've estimated this task already. Given what we know now (esp when implementing BelongsTo, are we still good with this estimate?
Activity
[-][Relation] Supports HasOne[/-][+][Relation] Supports HasOne relation[/+]dhmlau commentedon Oct 1, 2018
Cross posting in #1449 (comment) from @elv1s:
Currently
hasOneis not part of our Q1 roadmap. So I have 2 questions:hasOnesupport?hasOnein?EDIT: I realized that we've estimated this task already. Given what we know now (esp when implementing
BelongsTo, are we still good with this estimate?elv1s commentedon Oct 3, 2018
We are developing a POC with LB3 right now. If we move to LB4 we would need
hasOnerelationships early 2019.b-admike commentedon Dec 19, 2018
Closing as done.