Jon Johnson
Jon Johnson
Unfortunately because of the upstream assertion this is going to be difficult to use either way because `{{ref` may only **stop working** when some set of re-rendering conditions is met...
I agree, that message is very difficult to debug. On the other hand running all modifier in a new transaction (or with `run.next()` causes timing issues that get no visible...
I'm not super into the global refs part of this proposal, but I don't mind. I'm worried about throwing an error when unset, I think that would make it more...
I'm not sure how returning `null` aligns with `and will throw error if property does not yet set`. Am I reading this wrong?
@kategengler any interest in this, or should I go ahead and close?
Thanks for catching that @michaelchadwick, I'd forgotten to put that in my todo notes. Got it now!
This got quite out of hand, code wise, the individual commits hopefully provide some context. Unfortunately the UI concept changed half way through so some of the early commits are...
I like it on sessions, needs some attention on course objectives (and probably generically shouldn't specify it's own background, but should fade into whatever is behind it if possible)
This may prove tricky because it's not an event for the user. The event detail routes expect to know and load the current user unless the event it a school...
I think what you'd need to do is extract the information from the event slug and load the offering and other data needed to create a school event slug, then...