shamarifeaster / templar Goto Github PK

State.comilationThreadCnt is hitting 0 and the final block is running and then threads are returning resulting in the subject line.

bind the same list to multiple selects in a scope and only the last instance will render.

A user may want to for changes to a DMA that is not bound to the DOM, but exists strictly for book keeping purposes. When changed this book keeping may trigger some change in the DOM or cascade the change through the application state.

Current;y, interpolate() does not dispatch event listeners unless the event object has a type (ie a tagName).

`
${{$item}}.request.amt 's spent ``

"$" before works but text after attrib is erased

Might also want to think about giving current selection ;name' and 'value' properties.

STR: My Ads -> Pick and ad -> View

Notice the ad category missing in an unpredictable fashion.

Currently Templar sets lots of listeners but doesn't unbind them. Also it doesn't provide an APi to allow user to cleanup listeners bound to repeats.

I noticed when changing partial names that their listeners failed silently. In a large project this would be time consuming to track down the silent fails. Logging this would help.

templar-interpolation-sort tests failing when this case is executed,

We do not have access to the surrounding repeater's index property while inside the nested repeater.

Do def checking in the while loop of dereferenceAttribute() to stop this issue

When using an array length prop as the value, the attribute is not re-evaluating on change of the array length.

See: partials/Ad-Search/ad-list.html

Changing select preprocessing to allow for explicit repeating of option nodes.

The user would benefit from being able to distinguish whether a select attribute has changed due to a.) a clobber-set (as with a cascade) b.) a user selections c.) programmatic setting through 'current_selection.'

I want to be able to declare functions as properties of a component. this would keep me from having to redefine inner functions on every call to onCreate.

If I have a large, unpaged repeat and I change the state of an index far down the page,
the rebuilding of the entire repeat a.) causes the repeat to flash and b.) scrolls the user
up to the top of the page.

It seems the time has finally come for me to address my "scorched earth" repeat methodology

This would allow Templar to diff the current state from the requested state and load the diffs. This would reduce unnecessary compilation and server requests if those handlers had out bound requests.

the fix is listening for onchange as well as keyup

<a onclick="{{Example.handlers.clickBtn}}">clcik Me</a>

misspelled 'partial' and got no warning.

Rather than destroying and rebuilding the DOM on repeat attribute update, Templar should re-interpolate cached nodes in existing DOM.

commit b11f5cd is a partial step towards this.

We could store a partial template and fetch from the cache. This would reduce network requests for redundant templates (ie, nothing has changed in the template)

When routes being fetched, if one of the partials has a "dat-apl-default" in it
, the compiler spawns a fetch thread which may come back after the completion of the original
fetch chain. If the default shares the same target it will clobber the partial from
the fetch chain.

STR (steps to reproduce): click "My Ads" and notice that "Wall" comes up from time to time.