reactive

The Storybook API has changed quite a lot since Solid's Storybook docs were written in 2019. It would be really helpful (and I think go a loooong way toward helping drive adoption, long-term) if Solid could:

1. Update the docs to reflect the latest Storybo

Play Version

2.8.8

API

Java / SyncCacheApi

Operating System

Ubuntu 20.04 LTS

Linux 5.11.0-25-generic #27-Ubuntu SMP Fri Jul 9 23:06:29 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

JDK

openjdk version "1.8.0_292"
OpenJDK Runtime Environment (build 1.8.0_292-8u292-b10-0ubuntu1-b10)
OpenJDK 64-Bit Server VM (build 25.292-b10, mixed mode)

current return queueOfferResult == QueueOfferResult.enqueued();

Description

If we use io.quarkus.runtime.annotations.RegisterForReflection#classNames to register classes for reflection it does not register classes up in the hierarchy.

On the other hand, if we use -H:ReflectionConfigurationFiles, it does register the full class hierarchy.

Implementation ideas

I think we should look for the full hierarchy here: https://github.com/quarkusio/qu

Is there a way to export / import(restore) database.

看了fish-redux的todoList demo，发现里面连接全局状态的方法是使用visitor

visitor: (String path, Page<Object, dynamic> page) {
      /// 只有特定的范围的 Page 才需要建立和 AppStore 的连接关系
      /// 满足 Page<T> ，T 是 GlobalBaseState 的子类
      if (page.isTypeof<GlobalBaseState>()) {
        /// 建立 AppStore 驱动 PageStore 的单向数据连接
        /// 1. 参数1 AppStore
        /// 2. 参数2 当 AppStore.state 变化时, PageStore.state 该如何变化
     

jasmine-marbles should be 0.9.1 to go along with RxJS 7 for the generated examples.

https://github.com/ngrx/platform/blob/master/projects/ngrx.io/tools/examples/shared/boilerplate/cli/package.js

aside with FAIL_FAST.

i'm attempting to write a health check for a service that uses watermill and i'd like to be able to easily determine if the router is still up and running

Router exposes a channel at .Running(), and it's possible to infer if the router is closed with a little indirection:

running := false
go func() {
  r := router.Running()

  for {
    if _, open := <-r; open {
      running 

Correct me if I'm wrong, but it seems to me that different effector-vue APIs (especially Options API vs. Hooks API) assume different Vue versions.

For example, I tried to use Hooks API in combination with Vue 2 & @vue/composition-api but it won't compile because it tries to import composition functions directly from vue module (as in Vue 3) instead of @vue/compositon-api module (as in V

We have a couple of combinations of let and global that are not analyzed correctly, like:

let
	a = 1
	global a = 2
end

defines a global a, but Pluto prioritizes the let block.

@test_broken means that we still need to fix it:

https://github.com/fonsp/Pluto.jl/blob/c1d23122845e7864ef3dfe15a8428366c98f95eb/test/ExpressionExplorer.jl#L368-L379

This is a good firs

The idea is to be able to write the following to override the log configuration in dev-mode.

lagomDevSettings ++= Seq(
  "logger.resource" -> "logback-dev.xml"
)