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

ActorAdapter will ignore null message with "Adapter function returned null which is not valid as an .."

However, this seems not be documented. For instance, scaladoc/javadoc of pipeToSelf could mention it as well as any other place where adapters are used.

We use sbt-dynver to set the version for the Play project based on git tags.
E.g. when you run sbt in the Play project folder you will see:

// If you haven't you need to get the Play framework source code
git clone git@github.com:playframework/playframework.git
cd ./playframework

// You are in the master branch now, from which we want to rele

Description

This refers to the quarkus-opentelemetry extension.

We have opted for using a custom io.opentelemetry.sdk.trace.samplers.Sampler CDI Bean in order to extend the existing sampling logic.
As stated in the documentation, this means that the quarkus.opentelemetry.tracer.suppress-non-application-uris option has no effect, so that the logic for suppressing non-application uris

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 该如何变化
     

Information

A question that I frequently see on various channels, is how to implement an effect without parameters.
Because this seems to be the number one question, I propose to add an example to the docs.

Documentation page

https://ngrx.io/guide/component-store/effect

I would be willing to submit a PR to fix this issue

• Yes
• No

It would be nice if each operator Javadoc could clearly define the backpressure behaviour.

RxJava does something like this, e.g. http://reactivex.io/RxJava/javadoc/io/reactivex/Flowable.html#flatMap-io.reactivex.functions.Function-

This comment says that the message ID is optional,
but for SQL transport it is a mandatory attribute,
in turn it causes misunderstanding?

Is it possible to fix it or did I get something wrong?

https://github.com/ThreeDotsLabs/watermill/blob/b9928e750ba673cf93d442db88efc04706f67388/message/message.go#L20
https://github.com/ThreeDotsLabs/watermill/blob/b9928e750ba673cf93d442db88efc04706f6

We currently use some internal Pkg API to make https://github.com/fonsp/Pluto.jl/wiki/%F0%9F%8E%81-Package-management work, we we should try to avoid as much as possible. Take a look at src/packages/PkgCompat.jl to learn more, the compatibility issues are pretty well documented.

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

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"
)

With each release now, we would have to do asyncapi/website#720

The manual changes introduced in ☝🏼 PR should be automated, basically this workflow needs to be extended.