Library warning messages display when the app is compiled

[nyemiks]

I have been able to do a test app that uses this library in a re-frame application. I was only able to use the low level api to start and stop the state machine. The app runs using fsm in closed mode. My only concern is the warning messages that display anytime the source code is recompiled. See the trace below

pushd c:\Users\nyemi\Documents\react\myproject2\fetchimagefsm3 & npx.cmd shadow-cljs -d cider/cider-nrepl:0.47.1 watch :app & popd
shadow-cljs - config: c:\Users\nyemi\Documents\react\myproject2\fetchimagefsm3\shadow-cljs.edn
shadow-cljs - socket connect failed, server process dead?
shadow-cljs - HTTP server available at http://localhost:8280
shadow-cljs - HTTP server available at http://localhost:8290
shadow-cljs - server version: 2.26.2 running at http://localhost:9630
shadow-cljs - nREPL server started on port 8777
shadow-cljs - watching build :app
[:app] Configuring build.
[:app] Compiling ...
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
[:app] Build completed. (531 files, 1 compiled, 2 warnings, 40.14s)

------ WARNING #1 - :protocol-invalid-method -----------------------------------
Resource: re_statecharts/core.cljc:106:1

103 | (when-let [new-db (transition db machine opts fsm-event data more-data)]
104 | {:db new-db})))
105 |
106 | (deftype Scheduler [fsm-id ids clock open?]
-------^------------------------------------------------------------------------
Bad method signature in protocol implementation, delayed/IScheduler schedule does not declare arity 3

107 | delayed/IScheduler
108 | (schedule [_ event delay]
109 | (let [id (clock/setTimeout clock #(f/dispatch (if open?
110 | event

------ WARNING #2 - :protocol-invalid-method -----------------------------------
Resource: re_statecharts/core.cljc:106:1

103 | (when-let [new-db (transition db machine opts fsm-event data more-data)]
104 | {:db new-db})))
105 |
106 | (deftype Scheduler [fsm-id ids clock open?]
-------^------------------------------------------------------------------------
Bad method signature in protocol implementation, delayed/IScheduler unschedule does not declare arity 2

107 | delayed/IScheduler
108 | (schedule [_ event delay]
109 | (let [id (clock/setTimeout clock #(f/dispatch (if open?
110 | event

Hope this is not going to be a problem ?

I intend to use the library for a project. It certainly makes using clj state chart easier.

I need confirmation on this. I have two more queries to ask about this library. I will raise separate issues for them.