Nikky
10/20/2020, 6:05 PMStore::apply
does not seem to exist anymore
and andThen
i guessnapperley
11/01/2020, 11:47 PMnapperley
11/03/2020, 2:06 AMnapperley
11/04/2020, 2:08 AMpabl0rg
11/20/2020, 3:19 PMBig Chungus
12/04/2020, 4:23 PMchristophsturm
12/04/2020, 4:28 PMNikky
12/14/2020, 1:08 PMJilles van Gurp
12/15/2020, 9:44 AM{…}
"cause_us9j0c$_0": TypeError: NetworkError when attempting to fetch resource.
"message_q7r8iu$_0": "Fail to fetch"
name: "Error"
stack: "captureStack@webpack-internal:///./kotlin-dce-dev/kotlin.js:39116:27\nError_0@webpack-internal:///./kotlin-dce-dev/kotlin.js:39410:14\ncommonFetch$lambda$lambda_1/<@webpack-internal:///./kotlin-dce-dev/ktor-ktor-client-core-jsLegacy.js:17565:68\npromise callback*commonFetch$lambda/<@webpack-internal:///./kotlin-dce-dev/ktor-ktor-client-core-jsLegacy.js:17581:11\nsuspendCancellableCoroutine$lambda_1/<@webpack-internal:///./kotlin-dce-dev/ktor-ktor-client-core-jsLegacy.js:17547:16\nCoroutine$commonFetch.prototype.doResume@webpack-internal:///./kotlin-dce-dev/ktor-ktor-client-core-jsLegacy.js:17602:116\ncommonFetch@webpack-internal:///./kotlin-dce-dev/ktor-ktor-client-core-jsLegacy.js:17630:23\nCoroutine$execute_dkgphz$.prototype.doResume@webpack-internal:///./kotlin-dce-dev/ktor-ktor-client-core-jsLegacy.js:16974:25\nJsClientEngine.prototype.execute_dkgphz$@webpack-internal:///./kotlin-dce-dev/ktor-ktor-client-core-jsLegacy.js:17004:21\nCoroutine$HttpClientEngine$executeWithinCallContext$lambda.prototype.doResume@webpack-internal:///./kotlin-dce-dev/ktor-ktor-client-core-jsLegacy.js:1591:58\nCoroutineImpl.prototype.resumeWith_tl1gpc$@webpack-internal:///./kotlin-dce-dev/kotlin.js:39279:35\nDispatchedTask.prototype.run@webpack-internal:///./kotlin-dce-dev/kotlinx-coroutines-core.js:34823:22\nMessageQueue.prototype.process@webpack-internal:///./kotlin-dce-dev/kotlinx-coroutines-core.js:38215:15\nWindowMessageQueue$schedule$lambda/<@webpack-internal:///./kotlin-dce-dev/kotlinx-coroutines-core.js:38170:27\npromise callback*WindowMessageQueue.prototype.schedule@webpack-internal:///./kotlin-dce-dev/kotlinx-coroutines-core.js:38175:25\nMessageQueue.prototype.enqueue_771g0p$@webpack-internal:///./kotlin-dce-dev/kotlinx-coroutines-core.js:38202:10\nWindowDispatcher.prototype.dispatch_5bn72i$@webpack-internal:///./kotlin-dce-dev/kotlinx-coroutines-core.js:38126:16\nJsMainDispatcher.prototype.dispatch_5bn72i$@webpack-internal:///./kotlin-dce-dev/kotlinx-coroutines-core.js:37913:17\ndispatch@webpack-internal:///./kotlin-dce-dev/kotlinx-coroutines-core.js:34864:20\nCancellableContinuationImpl.prototype.dispatchResume_0@webpack-internal:///./kotlin-dce-dev/kotlinx-coroutines-core.js:1549:11\nCancellableContinuationImpl.prototype.completeResume_za3rmp$@webpack-internal:///./kotlin-dce-dev/kotlinx-coroutines-core.js:1647:8\nAbstractChannel$ReceiveElement.prototype.completeResumeReceive_11rb$@webpack-internal:///./kotlin-dce-dev/kotlinx-coroutines-core.js:6207:13\nArrayChannel.prototype.offerInternal_11rb$@webpack-internal:///./kotlin-dce-dev/kotlinx-coroutines-core.js:6938:28\nAbstractSendChannel.prototype.offer_11rb$@webpack-internal:///./kotlin-dce-dev/kotlinx-coroutines-core.js:5316:21\nChannelCoroutine.prototype.offer_11rb$@webpack-internal:///./kotlin-dce-dev/kotlinx-coroutines-core.js:7768:26\nWithEvents$subscribe$lambda$lambda/<@webpack-internal:///./kotlin-dce-dev/fritz2-core.js:3398:13\n"
<prototype>: Object { constructor: Error_0(), stack: "", … }
kotlinx-coroutines-core.js:37890
Harald Pehl
12/17/2020, 8:50 AMJilles van Gurp
12/17/2020, 4:32 PMupdate("xx")
println(current) // prints old value
update("yy")
delay(1000)
println(current) // prints yy
I solved it in my store by also putting the value in a private variable but that feels a bit ugly. Would it be possible to make this more consistent/less flaky?Hampus Londögård
12/19/2020, 12:30 PMBig Chungus
12/30/2020, 8:30 AMJilles van Gurp
01/19/2021, 1:39 PMNikky
01/20/2021, 6:35 PMswitch {
checked { switchState.data }
changes handledBy switchHandlerStore.flip
}
Nikky
01/27/2021, 4:50 PM<input type="file">
or so.. but i am not sure how to attach event listeners in fritz2.. and i feel like i am going down the wrong pathBig Chungus
02/04/2021, 4:39 PMNikky
02/16/2021, 12:22 PMList<String>
and a .renderEach
seems to not work on it.. did we overlook anything ?
our goal is to have a varaible amount of text fields that we can add or remove with a +/- button in a form
seems like .renderEach only gets called initally for the last value in the list and does not emit any html
i am wondering if we imported the wrong function
it kinda works if we do roles.data.renderEach
but now we have to make the update calls go though the store that contains the list of them and need to figure out which one we were editing, probably each if we just make a data class for it that contains the value and a unique id, but that seems like .. unnecessary complexityBig Chungus
02/19/2021, 10:37 PMHampus Londögård
02/22/2021, 9:33 AMBig Chungus
02/23/2021, 8:55 AMJilles van Gurp
02/23/2021, 3:34 PMNikky
03/02/2021, 4:08 PMJan Weidenhaupt
03/02/2021, 7:57 PMBig Chungus
03/08/2021, 4:06 PMJacob Otto
03/18/2021, 2:12 PMstyle.kt?2304:31 unable to insert rule in stylesheet: Failed to execute 'insertRule' on 'CSSStyleSheet': Failed to parse the rule ':-moz-ui-invalid{box-shadow:none;}'. DOMException: Failed to execute 'insertRule' on 'CSSStyleSheet': Failed to parse the rule ':-moz-ui-invalid{box-shadow:none;}'.
at eval (webpack-internal:///./kotlin-dce-dev/fritz2-styling-jsLegacy.js:3697:33)
at Array.eval (webpack-internal:///./kotlin-dce-dev/fritz2-styling-jsLegacy.js:3707:68)
at eval (webpack-internal:///../../node_modules/stylis/dist/stylis.mjs:68:5957)
at se (webpack-internal:///../../node_modules/stylis/dist/stylis.mjs:68:5651)
at Styling.addDynamicCss_puj7f4$ (webpack-internal:///./kotlin-dce-dev/fritz2-styling-jsLegacy.js:3763:7)
at Styling.resetCss_61zpoe$ (webpack-internal:///./kotlin-dce-dev/fritz2-styling-jsLegacy.js:3756:10)
at resetCss (webpack-internal:///./kotlin-dce-dev/fritz2-styling-jsLegacy.js:3790:27)
at new Theme$Companion (webpack-internal:///./kotlin-dce-dev/fritz2-styling-jsLegacy.js:11092:5)
at Theme$Companion_getInstance (webpack-internal:///./kotlin-dce-dev/fritz2-styling-jsLegacy.js:11109:7)
at SpacesContext.left_bcpvvc$ (webpack-internal:///./kotlin-dce-dev/fritz2-styling-jsLegacy.js:2926:16)
eval @ style.kt?2304:31
Big Chungus
03/19/2021, 1:03 PMtypealias StyledComponent<E> = RenderContext.(style: BoxParams.() -> Unit, block: E.() -> Unit) -> E
fun <E> styled(component: BasicComponent<E>): StyledComponent<E> = { style, block ->
(component.styled(styling = style))(block)
}
//usage
fun RenderContext.preview() {
styled(::div)({
// div style
}) {
// div code and inner layout
div {
// child unstyled div
}
}
}
Jan Weidenhaupt
03/19/2021, 1:46 PMnapperley
03/21/2021, 10:25 PMJacob Otto
03/26/2021, 10:22 AMJacob Otto
03/26/2021, 10:22 AMBig Chungus
03/26/2021, 10:24 AMJacob Otto
03/26/2021, 10:30 AMposition(
sm = { fixed {
left { "50%" }
*** I WANT TO HAVE IT HERE ***
} },
md = { fixed { left { none } } }
)
css(sm = "transform: translate(-50%, 0%);", md = "transform: translate(0%, 0%);")
😀Big Chungus
03/26/2021, 10:58 AMJacob Otto
03/26/2021, 11:32 AMChristian Hausknecht
03/29/2021, 8:38 AM// somehow within a styling context - NOT A WORKING EXAMPLE, just a sketch ;-)
sm {
position { fixed { left { "50%" } } }
css("transform: translate(-50%, 0%)")}
md {
position { fixed { left { none } } }
css("transform: translate(0%, 0%)")
}
On the other hand one might argue, that with the current approach you clearly can discover for each function separately, how it behaves for different breakpoints.
But your solution is the currently supported one and quite useable imho.Big Chungus
03/29/2021, 1:16 PM