status-im
/
status-react
mirror of https://github.com/status-im/status-react.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity
status-react/nix/deps/clojure/deps.list

176 lines
10 KiB
Plaintext
Raw Normal View History

dx(debug)_: Add FlowStorm, a tracing debugger for Clojure(Script) (#20054) Adds FlowStorm https://github.com/flow-storm/flow-storm-debugger v3.7.5, a well known (tracing) debugger for Clojure(Script). With FlowStorm, you can debug almost any cljs function in status-mobile. And although it is not as capable as on the JVM, its main features work well enough. How do I use it? Please, check the markdown diff in this PR: doc/debugging.md. When would you use FlowStorm in status-mobile? You can use it all the time if you want, but FlowStorm can be a powerful tool to understand complex pieces of code. Consider those large subscriptions or event handlers. Or all those components with lots of bindings and calculations. Understanding some of these things is no easy task, even with a REPL. It is not a replacement for re-frisk, those are very different tools and each have their place. Resources: - Repository: https://github.com/flow-storm/flow-storm-debugger - Documentation: https://flow-storm.github.io/flow-storm-debugger - Features: https://github.com/flow-storm/flow-storm-debugger#features - YouTube demos: https://github.com/flow-storm/flow-storm-debugger#some-demo-videos-newers-at-the-top
2024-06-03 22:47:10 +00:00
aopalliance/aopalliance/1.0/aopalliance-1.0.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
args4j/args4j/2.33/args4j-2.33.jar
babashka/fs/0.2.16/fs-0.2.16.jar
Add universal QR scanner via common router Rename events Add router to handle all links Use router in add new chat Unify universal link and universal qr with router Add icon for universal scanner Update tests Now routing is tested in routing PR lint Cleanup QA fixes Scan own profile Handle more EIP Fix wallet scanner Fix stack for view profile in UL Signed-off-by: Gheorghe Pinzaru <feross95@gmail.com>
2020-07-30 09:39:55 +00:00
bidi/bidi/2.1.6/bidi-2.1.6.jar
use shadow-cljs Signed-off-by: Jakub Sokołowski <jakub@status.im> Signed-off-by: yenda <eric@status.im>
2019-09-07 12:57:22 +00:00
binaryage/env-config/0.2.2/env-config-0.2.2.jar
Upgrade shadow-cljs and ClojureScript (#15417) This commit upgrades Shadow CLJS from 2.11.16 (released on Feb/21) to latest 2.25.0 (Jul/23), so ~1.5 years worth of upgrades. By upgrading shadow we can finally use the latest major Clojure version 1.11.x. Why upgrade shadow? - Shadow CLJS controls the ClojureScript version we can use. In order to use the latest major Clojure version we must upgrade Shadow CLJS. - Shadow CLJS releases new versions very frequently, and if you take a look at its changelog https://github.com/thheller/shadow-cljs/blob/master/CHANGELOG.md, you'll see it had tons and tons of bug fixes over the years. I hope some of them help improve the DX for certain contributors who recently reported issues with it. - Clojure 1.11 brings new features, bug fixes and even performance improvements (although I think the performance mostly impacts Clojure on the JVM). See the changelog https://github.com/clojure/clojure/blob/master/changes.md#changes-to-clojure-in-version-1110 Things that can be beneficial to us, or are interesting nonetheless: - New :as-alias to be used in require, which is like :as but does not require the namespace to load. This means namespaced keywords using :as-alias can't cause circular dependency errors. This feature would very useful if we used namespaced keywords, but we don't, so... https://github.com/clojure/clojure/blob/master/changes.md#22-as-alias-in-require - New macros run-test and run-test-var to run single test with fixtures and report. - New iteration function, useful for processing paginated data. https://www.abhinavomprakash.com/posts/clojure-iteration/ - New update-keys function: applies a function to every key in a map. - New update-vals function: applies a function to every value in a map. Examples for update-vals and update-keys. They should perform better than the common reduce-kv approach since they use a transient data structure. (let [m {:a 1 :b 2}] (update-vals m inc)) ; => {:a 2, :b 3} (let [m {:a 1 :b 2}] (update-keys m name)) ; => {"a" 1, "b" 2} Why change namespaces within __tests__ directories? Any namespace with the word --tests-- throws an error, like the one below. I didn't bother investigating why, so I changed the guidelines to reflect the new convention. It's probably related to the double dashes in the name. Namespace quo2.components.dividers.--tests--.divider-label-component-spec has a segment starting with an invalid JavaScript identifier at line 1
2023-07-28 16:40:54 +00:00
binaryage/oops/0.7.2/oops-0.7.2.jar
Introduce malli library (#17867) This commit is the foundational step to start using malli (https://github.com/metosin/malli) in this project. Take in consideration we will only be able to realize malli's full power in future iterations. For those without context: the mobile team watched a presentation about malli and went through a light RFC to put everyone on the same page, among other discussions here and there in PRs. To keep things relatively short: 1. Unit, integration and component tests will short-circuit (fail) when inputs/outputs don't conform to their respective function schemas (CI should fail too). 2. Failed schema checks will not block the app from initializing, nor throw an exception that would trigger the LogBox. Exceptions are only thrown in the scope of automated tests. 3. There's zero performance impact in production code because we only instrument. Instrumentation is removed from the compiled code due to the usage of "^boolean js.goog/DEBUG". 4. We shouldn't expect any meaningful slowdown during development. **What are we instrumenting in this PR?** Per our team's agreement, we're only instrumenting the bare minimum to showcase 2 examples. - Instrument a utility function utils.money/format-amount using the macro approach. - Instrument a quo component quo.components.counter.step.view/view using the functional approach. Both approaches are useful, the functional approach is powerful and allow us to instrument anonymous functions, like the ones we pass to subscriptions or event handlers, or the higher-order function quo.theme/with-theme. The macro approach is perfect for functions already defined with defn. **I evaluated the schema or function in the REPL but nothing changes** - If you evaluate the source function, you need to evaluate schema/=> or schema/instrument as well. - Remember to *var quote* when using schema/instrument. - You must call "(status-im2.setup.schema/setup!)" after any var is re-instrumented. It's advisable to add a keybinding in your editor to send this expression automatically to the CLJS REPL, or add the call at the end of the namespace you are working on (similar to how some devs add "(run-tests)" at the end of test namespaces). **Where should schemas be defined?** For the moment, we should focus on instrumenting quo components, so define each function schema in the same namespace as the component's public "view" var. To be specific: - A schema used only to instrument a single function and not used elsewhere, like a quo component schema, wouldn't benefit from being defined in a separate namespace because that would force the developer to constantly open two files instead of one to check function signatures. - A common schema reused across the repo, like ":schema.common/theme" should be registered in the global registry "schema.registry" so that consumers can just refer to it by keyword, as if it was a built-in malli schema. - A common schema describing status-go entities like message, notification, community, etc can be stored either in the respective "src/status_im2/contexts/*" or registered globally, or even somewhere else. This is yet to be defined, but since I chose not to include schemas for them, we can postpone this guideline.
2023-11-18 14:04:48 +00:00
borkdude/dynaload/0.3.5/dynaload-0.3.5.jar
borkdude/edamame/1.3.23/edamame-1.3.23.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
borkdude/sci.impl.reflector/0.0.1/sci.impl.reflector-0.0.1.jar
[#14689] Link previews in chat (#14771) * Initial * Link fetching * Post-merge fix
2023-01-18 21:43:26 +00:00
camel-snake-kebab/camel-snake-kebab/0.4.3/camel-snake-kebab-0.4.3.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
cheshire/cheshire/5.11.0/cheshire-5.11.0.jar
dx(debug)_: Add FlowStorm, a tracing debugger for Clojure(Script) (#20054) Adds FlowStorm https://github.com/flow-storm/flow-storm-debugger v3.7.5, a well known (tracing) debugger for Clojure(Script). With FlowStorm, you can debug almost any cljs function in status-mobile. And although it is not as capable as on the JVM, its main features work well enough. How do I use it? Please, check the markdown diff in this PR: doc/debugging.md. When would you use FlowStorm in status-mobile? You can use it all the time if you want, but FlowStorm can be a powerful tool to understand complex pieces of code. Consider those large subscriptions or event handlers. Or all those components with lots of bindings and calculations. Understanding some of these things is no easy task, even with a REPL. It is not a replacement for re-frisk, those are very different tools and each have their place. Resources: - Repository: https://github.com/flow-storm/flow-storm-debugger - Documentation: https://flow-storm.github.io/flow-storm-debugger - Features: https://github.com/flow-storm/flow-storm-debugger#features - YouTube demos: https://github.com/flow-storm/flow-storm-debugger#some-demo-videos-newers-at-the-top
2024-06-03 22:47:10 +00:00
cider/cider-nrepl/0.31.0/cider-nrepl-0.31.0.jar
cider/piggieback/0.4.1/piggieback-0.4.1.jar
Upgrade clj-kondo to 2024.03.13 (#19930) This PR upgrades clj-kondo (our Clojure linter) from v2023-09-07 to v2024-03-13, so ~6 months of development updates. You can check out the changes starting at https://github.com/clj-kondo/clj-kondo/blob/master/CHANGELOG.md#20231020. Nothing terribly useful to us this time, but as usual, clj-kondo can catch more problems and more reliably than before.
2024-05-09 15:04:31 +00:00
clj-kondo/clj-kondo/2024.03.13/clj-kondo-2024.03.13.jar
Upgrade Clojure libraries (#17690) Upgrades and cleans up all production Clojure dependencies and 1 dev-only dependency (com.taoensso/tufte). - Remove warning "WARNING: update-keys already refers to: #'clojure.core/update-keys in namespace: io.aviso.exception" - Remove hickory and mvxcvi/alphabase dependencies they are not used. - Upgrade com.taoensso/tufte from 2.1.0 to 2.6.3 - Upgrade transit-cljs from 0.8.248 to 0.8.280 - Upgrade cljs-bean from 1.3.0 to 1.9.0 - Remove workaround for com.taoensso/timbre in shadow-cljs.edn - Upgrade com.taoensso/timbre from 4.10 (Status fork) to 6.3.1
2023-10-20 23:47:23 +00:00
cljs-bean/cljs-bean/1.9.0/cljs-bean-1.9.0.jar
hot reload and re-frisk 1.3.1 Signed-off-by: Andrey Shovkoplyas <motor4ik@gmail.com>
2020-05-03 14:14:02 +00:00
clout/clout/2.1.2/clout-2.1.2.jar
use shadow-cljs Signed-off-by: Jakub Sokołowski <jakub@status.im> Signed-off-by: yenda <eric@status.im>
2019-09-07 12:57:22 +00:00
com/andrewmcveigh/cljs-time/0.5.2/cljs-time-0.5.2.jar
com/bhauman/cljs-test-display/0.1.1/cljs-test-display-0.1.1.jar
dx(debug)_: Add FlowStorm, a tracing debugger for Clojure(Script) (#20054) Adds FlowStorm https://github.com/flow-storm/flow-storm-debugger v3.7.5, a well known (tracing) debugger for Clojure(Script). With FlowStorm, you can debug almost any cljs function in status-mobile. And although it is not as capable as on the JVM, its main features work well enough. How do I use it? Please, check the markdown diff in this PR: doc/debugging.md. When would you use FlowStorm in status-mobile? You can use it all the time if you want, but FlowStorm can be a powerful tool to understand complex pieces of code. Consider those large subscriptions or event handlers. Or all those components with lots of bindings and calculations. Understanding some of these things is no easy task, even with a REPL. It is not a replacement for re-frisk, those are very different tools and each have their place. Resources: - Repository: https://github.com/flow-storm/flow-storm-debugger - Documentation: https://flow-storm.github.io/flow-storm-debugger - Features: https://github.com/flow-storm/flow-storm-debugger#features - YouTube demos: https://github.com/flow-storm/flow-storm-debugger#some-demo-videos-newers-at-the-top
2024-06-03 22:47:10 +00:00
com/cognitect/aws/api/0.8.612/api-0.8.612.jar
com/cognitect/aws/endpoints/1.1.12.321/endpoints-1.1.12.321.jar
com/cognitect/aws/s3/822.2.1145.0/s3-822.2.1145.0.jar
com/cognitect/http-client/1.0.115/http-client-1.0.115.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
com/cognitect/transit-clj/1.0.329/transit-clj-1.0.329.jar
Upgrade Clojure libraries (#17690) Upgrades and cleans up all production Clojure dependencies and 1 dev-only dependency (com.taoensso/tufte). - Remove warning "WARNING: update-keys already refers to: #'clojure.core/update-keys in namespace: io.aviso.exception" - Remove hickory and mvxcvi/alphabase dependencies they are not used. - Upgrade com.taoensso/tufte from 2.1.0 to 2.6.3 - Upgrade transit-cljs from 0.8.248 to 0.8.280 - Upgrade cljs-bean from 1.3.0 to 1.9.0 - Remove workaround for com.taoensso/timbre in shadow-cljs.edn - Upgrade com.taoensso/timbre from 4.10 (Status fork) to 6.3.1
2023-10-20 23:47:23 +00:00
com/cognitect/transit-cljs/0.8.280/transit-cljs-0.8.280.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
com/cognitect/transit-java/1.0.362/transit-java-1.0.362.jar
Upgrade Clojure libraries (#17690) Upgrades and cleans up all production Clojure dependencies and 1 dev-only dependency (com.taoensso/tufte). - Remove warning "WARNING: update-keys already refers to: #'clojure.core/update-keys in namespace: io.aviso.exception" - Remove hickory and mvxcvi/alphabase dependencies they are not used. - Upgrade com.taoensso/tufte from 2.1.0 to 2.6.3 - Upgrade transit-cljs from 0.8.248 to 0.8.280 - Upgrade cljs-bean from 1.3.0 to 1.9.0 - Remove workaround for com.taoensso/timbre in shadow-cljs.edn - Upgrade com.taoensso/timbre from 4.10 (Status fork) to 6.3.1
2023-10-20 23:47:23 +00:00
com/cognitect/transit-js/0.8.874/transit-js-0.8.874.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
com/fasterxml/jackson/core/jackson-core/2.13.3/jackson-core-2.13.3.jar
com/fasterxml/jackson/dataformat/jackson-dataformat-cbor/2.13.3/jackson-dataformat-cbor-2.13.3.jar
com/fasterxml/jackson/dataformat/jackson-dataformat-smile/2.13.3/jackson-dataformat-smile-2.13.3.jar
com/github/javaparser/javaparser-core/3.25.3/javaparser-core-3.25.3.jar
dx(debug)_: Add FlowStorm, a tracing debugger for Clojure(Script) (#20054) Adds FlowStorm https://github.com/flow-storm/flow-storm-debugger v3.7.5, a well known (tracing) debugger for Clojure(Script). With FlowStorm, you can debug almost any cljs function in status-mobile. And although it is not as capable as on the JVM, its main features work well enough. How do I use it? Please, check the markdown diff in this PR: doc/debugging.md. When would you use FlowStorm in status-mobile? You can use it all the time if you want, but FlowStorm can be a powerful tool to understand complex pieces of code. Consider those large subscriptions or event handlers. Or all those components with lots of bindings and calculations. Understanding some of these things is no easy task, even with a REPL. It is not a replacement for re-frisk, those are very different tools and each have their place. Resources: - Repository: https://github.com/flow-storm/flow-storm-debugger - Documentation: https://flow-storm.github.io/flow-storm-debugger - Features: https://github.com/flow-storm/flow-storm-debugger#features - YouTube demos: https://github.com/flow-storm/flow-storm-debugger#some-demo-videos-newers-at-the-top
2024-06-03 22:47:10 +00:00
com/github/jpmonettas/flow-storm-inst/3.7.5/flow-storm-inst-3.7.5.jar
com/github/jpmonettas/hansel/0.1.78/hansel-0.1.78.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
com/google/auto/value/auto-value-annotations/1.6/auto-value-annotations-1.6.jar
com/google/code/findbugs/jsr305/3.0.2/jsr305-3.0.2.jar
com/google/code/gson/gson/2.9.1/gson-2.9.1.jar
Upgrade clj-kondo to 2024.03.13 (#19930) This PR upgrades clj-kondo (our Clojure linter) from v2023-09-07 to v2024-03-13, so ~6 months of development updates. You can check out the changes starting at https://github.com/clj-kondo/clj-kondo/blob/master/CHANGELOG.md#20231020. Nothing terribly useful to us this time, but as usual, clj-kondo can catch more problems and more reliably than before.
2024-05-09 15:04:31 +00:00
com/googlecode/json-simple/json-simple/1.1.1/json-simple-1.1.1.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
com/google/errorprone/error_prone_annotations/2.15.0/error_prone_annotations-2.15.0.jar
com/google/guava/failureaccess/1.0.1/failureaccess-1.0.1.jar
com/google/guava/guava/31.0.1-jre/guava-31.0.1-jre.jar
com/google/guava/listenablefuture/9999.0-empty-to-avoid-conflict-with-guava/listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar
dx(debug)_: Add FlowStorm, a tracing debugger for Clojure(Script) (#20054) Adds FlowStorm https://github.com/flow-storm/flow-storm-debugger v3.7.5, a well known (tracing) debugger for Clojure(Script). With FlowStorm, you can debug almost any cljs function in status-mobile. And although it is not as capable as on the JVM, its main features work well enough. How do I use it? Please, check the markdown diff in this PR: doc/debugging.md. When would you use FlowStorm in status-mobile? You can use it all the time if you want, but FlowStorm can be a powerful tool to understand complex pieces of code. Consider those large subscriptions or event handlers. Or all those components with lots of bindings and calculations. Understanding some of these things is no easy task, even with a REPL. It is not a replacement for re-frisk, those are very different tools and each have their place. Resources: - Repository: https://github.com/flow-storm/flow-storm-debugger - Documentation: https://flow-storm.github.io/flow-storm-debugger - Features: https://github.com/flow-storm/flow-storm-debugger#features - YouTube demos: https://github.com/flow-storm/flow-storm-debugger#some-demo-videos-newers-at-the-top
2024-06-03 22:47:10 +00:00
com/google/inject/guice/4.2.2/guice-4.2.2-no_aop.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
com/google/j2objc/j2objc-annotations/1.3/j2objc-annotations-1.3.jar
Add Promesa to simplify working with promises (#18767) * added promesa (clj) Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> * ref(resize): using promesa instead of passing cb Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> --------- Signed-off-by: Cristian Lungu <lungucristian95@gmail.com>
2024-03-04 11:59:52 +00:00
com/google/javascript/closure-compiler-unshaded/v20230802/closure-compiler-unshaded-v20230802.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
com/google/protobuf/protobuf-java/3.21.12/protobuf-java-3.21.12.jar
com/google/re2j/re2j/1.3/re2j-1.3.jar
Add Promesa to simplify working with promises (#18767) * added promesa (clj) Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> * ref(resize): using promesa instead of passing cb Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> --------- Signed-off-by: Cristian Lungu <lungucristian95@gmail.com>
2024-03-04 11:59:52 +00:00
commons-codec/commons-codec/1.15/commons-codec-1.15.jar
commons-fileupload/commons-fileupload/1.4/commons-fileupload-1.4.jar
commons-io/commons-io/2.11.0/commons-io-2.11.0.jar
compojure/compojure/1.5.2/compojure-1.5.2.jar
Upgrade clj-kondo to 2024.03.13 (#19930) This PR upgrades clj-kondo (our Clojure linter) from v2023-09-07 to v2024-03-13, so ~6 months of development updates. You can check out the changes starting at https://github.com/clj-kondo/clj-kondo/blob/master/CHANGELOG.md#20231020. Nothing terribly useful to us this time, but as usual, clj-kondo can catch more problems and more reliably than before.
2024-05-09 15:04:31 +00:00
com/taoensso/encore/3.68.0/encore-3.68.0.jar
com/taoensso/timbre/6.3.1/timbre-6.3.1.jar
com/taoensso/truss/1.11.0/truss-1.11.0.jar
com/taoensso/tufte/2.6.3/tufte-2.6.3.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
crypto-equality/crypto-equality/1.0.1/crypto-equality-1.0.1.jar
crypto-random/crypto-random/1.2.1/crypto-random-1.2.1.jar
use shadow-cljs Signed-off-by: Jakub Sokołowski <jakub@status.im> Signed-off-by: yenda <eric@status.im>
2019-09-07 12:57:22 +00:00
day8/re-frame/test/0.1.5/test-0.1.5.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
expound/expound/0.9.0/expound-0.9.0.jar
fipp/fipp/0.6.26/fipp-0.6.26.jar
Add Promesa to simplify working with promises (#18767) * added promesa (clj) Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> * ref(resize): using promesa instead of passing cb Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> --------- Signed-off-by: Cristian Lungu <lungucristian95@gmail.com>
2024-03-04 11:59:52 +00:00
funcool/promesa/11.0.678/promesa-11.0.678.jar
use shadow-cljs Signed-off-by: Jakub Sokołowski <jakub@status.im> Signed-off-by: yenda <eric@status.im>
2019-09-07 12:57:22 +00:00
hiccup/hiccup/1.0.5/hiccup-1.0.5.jar
hot reload and re-frisk 1.3.1 Signed-off-by: Andrey Shovkoplyas <motor4ik@gmail.com>
2020-05-03 14:14:02 +00:00
http-kit/http-kit/2.2.0/http-kit-2.2.0.jar
instaparse/instaparse/1.4.0/instaparse-1.4.0.jar
Upgrade Clojure libraries (#17690) Upgrades and cleans up all production Clojure dependencies and 1 dev-only dependency (com.taoensso/tufte). - Remove warning "WARNING: update-keys already refers to: #'clojure.core/update-keys in namespace: io.aviso.exception" - Remove hickory and mvxcvi/alphabase dependencies they are not used. - Upgrade com.taoensso/tufte from 2.1.0 to 2.6.3 - Upgrade transit-cljs from 0.8.248 to 0.8.280 - Upgrade cljs-bean from 1.3.0 to 1.9.0 - Remove workaround for com.taoensso/timbre in shadow-cljs.edn - Upgrade com.taoensso/timbre from 4.10 (Status fork) to 6.3.1
2023-10-20 23:47:23 +00:00
io/aviso/pretty/1.4.4/pretty-1.4.4.jar
dx(debug)_: Add FlowStorm, a tracing debugger for Clojure(Script) (#20054) Adds FlowStorm https://github.com/flow-storm/flow-storm-debugger v3.7.5, a well known (tracing) debugger for Clojure(Script). With FlowStorm, you can debug almost any cljs function in status-mobile. And although it is not as capable as on the JVM, its main features work well enough. How do I use it? Please, check the markdown diff in this PR: doc/debugging.md. When would you use FlowStorm in status-mobile? You can use it all the time if you want, but FlowStorm can be a powerful tool to understand complex pieces of code. Consider those large subscriptions or event handlers. Or all those components with lots of bindings and calculations. Understanding some of these things is no easy task, even with a REPL. It is not a replacement for re-frisk, those are very different tools and each have their place. Resources: - Repository: https://github.com/flow-storm/flow-storm-debugger - Documentation: https://flow-storm.github.io/flow-storm-debugger - Features: https://github.com/flow-storm/flow-storm-debugger#features - YouTube demos: https://github.com/flow-storm/flow-storm-debugger#some-demo-videos-newers-at-the-top
2024-06-03 22:47:10 +00:00
io/github/clojure/tools.build/0.9.4/tools.build-0.9.4.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
io/methvin/directory-watcher/0.17.1/directory-watcher-0.17.1.jar
io/replikativ/datalog-parser/0.2.25/datalog-parser-0.2.25.jar
Add Promesa to simplify working with promises (#18767) * added promesa (clj) Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> * ref(resize): using promesa instead of passing cb Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> --------- Signed-off-by: Cristian Lungu <lungucristian95@gmail.com>
2024-03-04 11:59:52 +00:00
io/undertow/undertow-core/2.3.10.Final/undertow-core-2.3.10.Final.jar
dx(debug)_: Add FlowStorm, a tracing debugger for Clojure(Script) (#20054) Adds FlowStorm https://github.com/flow-storm/flow-storm-debugger v3.7.5, a well known (tracing) debugger for Clojure(Script). With FlowStorm, you can debug almost any cljs function in status-mobile. And although it is not as capable as on the JVM, its main features work well enough. How do I use it? Please, check the markdown diff in this PR: doc/debugging.md. When would you use FlowStorm in status-mobile? You can use it all the time if you want, but FlowStorm can be a powerful tool to understand complex pieces of code. Consider those large subscriptions or event handlers. Or all those components with lots of bindings and calculations. Understanding some of these things is no easy task, even with a REPL. It is not a replacement for re-frisk, those are very different tools and each have their place. Resources: - Repository: https://github.com/flow-storm/flow-storm-debugger - Documentation: https://flow-storm.github.io/flow-storm-debugger - Features: https://github.com/flow-storm/flow-storm-debugger#features - YouTube demos: https://github.com/flow-storm/flow-storm-debugger#some-demo-videos-newers-at-the-top
2024-06-03 22:47:10 +00:00
javax/annotation/javax.annotation-api/1.3.2/javax.annotation-api-1.3.2.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
javax/annotation/jsr250-api/1.0/jsr250-api-1.0.jar
dx(debug)_: Add FlowStorm, a tracing debugger for Clojure(Script) (#20054) Adds FlowStorm https://github.com/flow-storm/flow-storm-debugger v3.7.5, a well known (tracing) debugger for Clojure(Script). With FlowStorm, you can debug almost any cljs function in status-mobile. And although it is not as capable as on the JVM, its main features work well enough. How do I use it? Please, check the markdown diff in this PR: doc/debugging.md. When would you use FlowStorm in status-mobile? You can use it all the time if you want, but FlowStorm can be a powerful tool to understand complex pieces of code. Consider those large subscriptions or event handlers. Or all those components with lots of bindings and calculations. Understanding some of these things is no easy task, even with a REPL. It is not a replacement for re-frisk, those are very different tools and each have their place. Resources: - Repository: https://github.com/flow-storm/flow-storm-debugger - Documentation: https://flow-storm.github.io/flow-storm-debugger - Features: https://github.com/flow-storm/flow-storm-debugger#features - YouTube demos: https://github.com/flow-storm/flow-storm-debugger#some-demo-videos-newers-at-the-top
2024-06-03 22:47:10 +00:00
javax/inject/javax.inject/1/javax.inject-1.jar
hot reload and re-frisk 1.3.1 Signed-off-by: Andrey Shovkoplyas <motor4ik@gmail.com>
2020-05-03 14:14:02 +00:00
javax/servlet/servlet-api/2.5/servlet-api-2.5.jar
use shadow-cljs Signed-off-by: Jakub Sokołowski <jakub@status.im> Signed-off-by: yenda <eric@status.im>
2019-09-07 12:57:22 +00:00
javax/xml/bind/jaxb-api/2.3.0/jaxb-api-2.3.0.jar
hot reload and re-frisk 1.3.1 Signed-off-by: Andrey Shovkoplyas <motor4ik@gmail.com>
2020-05-03 14:14:02 +00:00
medley/medley/0.8.2/medley-0.8.2.jar
Introduce malli library (#17867) This commit is the foundational step to start using malli (https://github.com/metosin/malli) in this project. Take in consideration we will only be able to realize malli's full power in future iterations. For those without context: the mobile team watched a presentation about malli and went through a light RFC to put everyone on the same page, among other discussions here and there in PRs. To keep things relatively short: 1. Unit, integration and component tests will short-circuit (fail) when inputs/outputs don't conform to their respective function schemas (CI should fail too). 2. Failed schema checks will not block the app from initializing, nor throw an exception that would trigger the LogBox. Exceptions are only thrown in the scope of automated tests. 3. There's zero performance impact in production code because we only instrument. Instrumentation is removed from the compiled code due to the usage of "^boolean js.goog/DEBUG". 4. We shouldn't expect any meaningful slowdown during development. **What are we instrumenting in this PR?** Per our team's agreement, we're only instrumenting the bare minimum to showcase 2 examples. - Instrument a utility function utils.money/format-amount using the macro approach. - Instrument a quo component quo.components.counter.step.view/view using the functional approach. Both approaches are useful, the functional approach is powerful and allow us to instrument anonymous functions, like the ones we pass to subscriptions or event handlers, or the higher-order function quo.theme/with-theme. The macro approach is perfect for functions already defined with defn. **I evaluated the schema or function in the REPL but nothing changes** - If you evaluate the source function, you need to evaluate schema/=> or schema/instrument as well. - Remember to *var quote* when using schema/instrument. - You must call "(status-im2.setup.schema/setup!)" after any var is re-instrumented. It's advisable to add a keybinding in your editor to send this expression automatically to the CLJS REPL, or add the call at the end of the namespace you are working on (similar to how some devs add "(run-tests)" at the end of test namespaces). **Where should schemas be defined?** For the moment, we should focus on instrumenting quo components, so define each function schema in the same namespace as the component's public "view" var. To be specific: - A schema used only to instrument a single function and not used elsewhere, like a quo component schema, wouldn't benefit from being defined in a separate namespace because that would force the developer to constantly open two files instead of one to check function signatures. - A common schema reused across the repo, like ":schema.common/theme" should be registered in the global registry "schema.registry" so that consumers can just refer to it by keyword, as if it was a built-in malli schema. - A common schema describing status-go entities like message, notification, community, etc can be stored either in the respective "src/status_im2/contexts/*" or registered globally, or even somewhere else. This is yet to be defined, but since I chose not to include schemas for them, we can postpone this guideline.
2023-11-18 14:04:48 +00:00
metosin/malli/0.13.0/malli-0.13.0.jar
mvxcvi/arrangement/2.1.0/arrangement-2.1.0.jar
use shadow-cljs Signed-off-by: Jakub Sokołowski <jakub@status.im> Signed-off-by: yenda <eric@status.im>
2019-09-07 12:57:22 +00:00
net/cgrand/macrovich/0.2.1/macrovich-0.2.1.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
net/java/dev/jna/jna/5.12.1/jna-5.12.1.jar
nrepl/bencode/1.1.0/bencode-1.1.0.jar
dx(debug)_: Add FlowStorm, a tracing debugger for Clojure(Script) (#20054) Adds FlowStorm https://github.com/flow-storm/flow-storm-debugger v3.7.5, a well known (tracing) debugger for Clojure(Script). With FlowStorm, you can debug almost any cljs function in status-mobile. And although it is not as capable as on the JVM, its main features work well enough. How do I use it? Please, check the markdown diff in this PR: doc/debugging.md. When would you use FlowStorm in status-mobile? You can use it all the time if you want, but FlowStorm can be a powerful tool to understand complex pieces of code. Consider those large subscriptions or event handlers. Or all those components with lots of bindings and calculations. Understanding some of these things is no easy task, even with a REPL. It is not a replacement for re-frisk, those are very different tools and each have their place. Resources: - Repository: https://github.com/flow-storm/flow-storm-debugger - Documentation: https://flow-storm.github.io/flow-storm-debugger - Features: https://github.com/flow-storm/flow-storm-debugger#features - YouTube demos: https://github.com/flow-storm/flow-storm-debugger#some-demo-videos-newers-at-the-top
2024-06-03 22:47:10 +00:00
nrepl/nrepl/1.0.0/nrepl-1.0.0.jar
Improve test failure readability (#18049) Problem: failed equality checks as in "(is (= expected actual))" will give a single, long line of output that for anything but the simplest data structures is unreadable by humans, and the output doesn't give a useful diff. Solution: use library https://github.com/nubank/matcher-combinators and its test directive "match?" which will pinpoint where two data structures differ. Then, instead of "(is (= ...", use "(is (match? expected actual)". It works beautifully. The library offers other nice matchers, but the majority of the time match? is sufficient. Can we use another test runner like Kaocha? kaocha-cljs2 (https://github.com/lambdaisland/kaocha-cljs2) would be able to print better test errors out of the box, among other features, but I have no clue if it would work well or at all in our stack (in theory yes, but it's a larger piece of work).
2023-12-05 20:20:54 +00:00
nubank/matcher-combinators/3.8.8/matcher-combinators-3.8.8.jar
Add Promesa to simplify working with promises (#18767) * added promesa (clj) Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> * ref(resize): using promesa instead of passing cb Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> --------- Signed-off-by: Cristian Lungu <lungucristian95@gmail.com>
2024-03-04 11:59:52 +00:00
org/apache/ant/ant/1.10.11/ant-1.10.11.jar
Upgrade clj-kondo to 2024.03.13 (#19930) This PR upgrades clj-kondo (our Clojure linter) from v2023-09-07 to v2024-03-13, so ~6 months of development updates. You can check out the changes starting at https://github.com/clj-kondo/clj-kondo/blob/master/CHANGELOG.md#20231020. Nothing terribly useful to us this time, but as usual, clj-kondo can catch more problems and more reliably than before.
2024-05-09 15:04:31 +00:00
org/apache/ant/ant-launcher/1.10.11/ant-launcher-1.10.11.jar
dx(debug)_: Add FlowStorm, a tracing debugger for Clojure(Script) (#20054) Adds FlowStorm https://github.com/flow-storm/flow-storm-debugger v3.7.5, a well known (tracing) debugger for Clojure(Script). With FlowStorm, you can debug almost any cljs function in status-mobile. And although it is not as capable as on the JVM, its main features work well enough. How do I use it? Please, check the markdown diff in this PR: doc/debugging.md. When would you use FlowStorm in status-mobile? You can use it all the time if you want, but FlowStorm can be a powerful tool to understand complex pieces of code. Consider those large subscriptions or event handlers. Or all those components with lots of bindings and calculations. Understanding some of these things is no easy task, even with a REPL. It is not a replacement for re-frisk, those are very different tools and each have their place. Resources: - Repository: https://github.com/flow-storm/flow-storm-debugger - Documentation: https://flow-storm.github.io/flow-storm-debugger - Features: https://github.com/flow-storm/flow-storm-debugger#features - YouTube demos: https://github.com/flow-storm/flow-storm-debugger#some-demo-videos-newers-at-the-top
2024-06-03 22:47:10 +00:00
org/apache/commons/commons-lang3/3.12.0/commons-lang3-3.12.0.jar
org/apache/httpcomponents/httpclient/4.5.13/httpclient-4.5.13.jar
org/apache/httpcomponents/httpcore/4.4.15/httpcore-4.4.15.jar
org/apache/maven/maven-artifact/3.8.6/maven-artifact-3.8.6.jar
org/apache/maven/maven-builder-support/3.8.6/maven-builder-support-3.8.6.jar
org/apache/maven/maven-core/3.8.6/maven-core-3.8.6.jar
org/apache/maven/maven-model/3.8.6/maven-model-3.8.6.jar
org/apache/maven/maven-model-builder/3.8.6/maven-model-builder-3.8.6.jar
org/apache/maven/maven-plugin-api/3.8.6/maven-plugin-api-3.8.6.jar
org/apache/maven/maven-repository-metadata/3.8.6/maven-repository-metadata-3.8.6.jar
org/apache/maven/maven-resolver-provider/3.8.6/maven-resolver-provider-3.8.6.jar
org/apache/maven/maven-settings/3.8.6/maven-settings-3.8.6.jar
org/apache/maven/maven-settings-builder/3.8.6/maven-settings-builder-3.8.6.jar
org/apache/maven/resolver/maven-resolver-api/1.8.2/maven-resolver-api-1.8.2.jar
org/apache/maven/resolver/maven-resolver-connector-basic/1.8.2/maven-resolver-connector-basic-1.8.2.jar
org/apache/maven/resolver/maven-resolver-impl/1.8.2/maven-resolver-impl-1.8.2.jar
org/apache/maven/resolver/maven-resolver-named-locks/1.8.2/maven-resolver-named-locks-1.8.2.jar
org/apache/maven/resolver/maven-resolver-spi/1.8.2/maven-resolver-spi-1.8.2.jar
org/apache/maven/resolver/maven-resolver-transport-file/1.8.2/maven-resolver-transport-file-1.8.2.jar
org/apache/maven/resolver/maven-resolver-transport-http/1.8.2/maven-resolver-transport-http-1.8.2.jar
org/apache/maven/resolver/maven-resolver-util/1.8.2/maven-resolver-util-1.8.2.jar
org/apache/maven/shared/maven-shared-utils/3.3.4/maven-shared-utils-3.3.4.jar
Upgrade clj-kondo to 2024.03.13 (#19930) This PR upgrades clj-kondo (our Clojure linter) from v2023-09-07 to v2024-03-13, so ~6 months of development updates. You can check out the changes starting at https://github.com/clj-kondo/clj-kondo/blob/master/CHANGELOG.md#20231020. Nothing terribly useful to us this time, but as usual, clj-kondo can catch more problems and more reliably than before.
2024-05-09 15:04:31 +00:00
org/babashka/sci/0.8.41/sci-0.8.41.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
org/babashka/sci.impl.types/0.0.2/sci.impl.types-0.0.2.jar
org/checkerframework/checker-qual/3.12.0/checker-qual-3.12.0.jar
org/clojure/clojure/1.11.1/clojure-1.11.1.jar
org/clojure/clojurescript/1.11.60/clojurescript-1.11.60.jar
org/clojure/core.async/1.5.648/core.async-1.5.648.jar
org/clojure/core.cache/1.0.225/core.cache-1.0.225.jar
org/clojure/core.memoize/1.0.253/core.memoize-1.0.253.jar
org/clojure/core.rrb-vector/0.1.2/core.rrb-vector-0.1.2.jar
org/clojure/core.specs.alpha/0.2.62/core.specs.alpha-0.2.62.jar
dx(debug)_: Add FlowStorm, a tracing debugger for Clojure(Script) (#20054) Adds FlowStorm https://github.com/flow-storm/flow-storm-debugger v3.7.5, a well known (tracing) debugger for Clojure(Script). With FlowStorm, you can debug almost any cljs function in status-mobile. And although it is not as capable as on the JVM, its main features work well enough. How do I use it? Please, check the markdown diff in this PR: doc/debugging.md. When would you use FlowStorm in status-mobile? You can use it all the time if you want, but FlowStorm can be a powerful tool to understand complex pieces of code. Consider those large subscriptions or event handlers. Or all those components with lots of bindings and calculations. Understanding some of these things is no easy task, even with a REPL. It is not a replacement for re-frisk, those are very different tools and each have their place. Resources: - Repository: https://github.com/flow-storm/flow-storm-debugger - Documentation: https://flow-storm.github.io/flow-storm-debugger - Features: https://github.com/flow-storm/flow-storm-debugger#features - YouTube demos: https://github.com/flow-storm/flow-storm-debugger#some-demo-videos-newers-at-the-top
2024-06-03 22:47:10 +00:00
org/clojure/data.int-map/1.2.1/data.int-map-1.2.1.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
org/clojure/data.json/2.4.0/data.json-2.4.0.jar
org/clojure/data.priority-map/1.1.0/data.priority-map-1.1.0.jar
dx(debug)_: Add FlowStorm, a tracing debugger for Clojure(Script) (#20054) Adds FlowStorm https://github.com/flow-storm/flow-storm-debugger v3.7.5, a well known (tracing) debugger for Clojure(Script). With FlowStorm, you can debug almost any cljs function in status-mobile. And although it is not as capable as on the JVM, its main features work well enough. How do I use it? Please, check the markdown diff in this PR: doc/debugging.md. When would you use FlowStorm in status-mobile? You can use it all the time if you want, but FlowStorm can be a powerful tool to understand complex pieces of code. Consider those large subscriptions or event handlers. Or all those components with lots of bindings and calculations. Understanding some of these things is no easy task, even with a REPL. It is not a replacement for re-frisk, those are very different tools and each have their place. Resources: - Repository: https://github.com/flow-storm/flow-storm-debugger - Documentation: https://flow-storm.github.io/flow-storm-debugger - Features: https://github.com/flow-storm/flow-storm-debugger#features - YouTube demos: https://github.com/flow-storm/flow-storm-debugger#some-demo-videos-newers-at-the-top
2024-06-03 22:47:10 +00:00
org/clojure/data.xml/0.2.0-alpha8/data.xml-0.2.0-alpha8.jar
Add Promesa to simplify working with promises (#18767) * added promesa (clj) Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> * ref(resize): using promesa instead of passing cb Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> --------- Signed-off-by: Cristian Lungu <lungucristian95@gmail.com>
2024-03-04 11:59:52 +00:00
org/clojure/google-closure-library/0.0-20230227-c7c0a541/google-closure-library-0.0-20230227-c7c0a541.jar
Upgrade clj-kondo to 2024.03.13 (#19930) This PR upgrades clj-kondo (our Clojure linter) from v2023-09-07 to v2024-03-13, so ~6 months of development updates. You can check out the changes starting at https://github.com/clj-kondo/clj-kondo/blob/master/CHANGELOG.md#20231020. Nothing terribly useful to us this time, but as usual, clj-kondo can catch more problems and more reliably than before.
2024-05-09 15:04:31 +00:00
org/clojure/google-closure-library-third-party/0.0-20230227-c7c0a541/google-closure-library-third-party-0.0-20230227-c7c0a541.jar
dx(debug)_: Add FlowStorm, a tracing debugger for Clojure(Script) (#20054) Adds FlowStorm https://github.com/flow-storm/flow-storm-debugger v3.7.5, a well known (tracing) debugger for Clojure(Script). With FlowStorm, you can debug almost any cljs function in status-mobile. And although it is not as capable as on the JVM, its main features work well enough. How do I use it? Please, check the markdown diff in this PR: doc/debugging.md. When would you use FlowStorm in status-mobile? You can use it all the time if you want, but FlowStorm can be a powerful tool to understand complex pieces of code. Consider those large subscriptions or event handlers. Or all those components with lots of bindings and calculations. Understanding some of these things is no easy task, even with a REPL. It is not a replacement for re-frisk, those are very different tools and each have their place. Resources: - Repository: https://github.com/flow-storm/flow-storm-debugger - Documentation: https://flow-storm.github.io/flow-storm-debugger - Features: https://github.com/flow-storm/flow-storm-debugger#features - YouTube demos: https://github.com/flow-storm/flow-storm-debugger#some-demo-videos-newers-at-the-top
2024-06-03 22:47:10 +00:00
org/clojure/java.classpath/1.0.0/java.classpath-1.0.0.jar
Improve test failure readability (#18049) Problem: failed equality checks as in "(is (= expected actual))" will give a single, long line of output that for anything but the simplest data structures is unreadable by humans, and the output doesn't give a useful diff. Solution: use library https://github.com/nubank/matcher-combinators and its test directive "match?" which will pinpoint where two data structures differ. Then, instead of "(is (= ...", use "(is (match? expected actual)". It works beautifully. The library offers other nice matchers, but the majority of the time match? is sufficient. Can we use another test runner like Kaocha? kaocha-cljs2 (https://github.com/lambdaisland/kaocha-cljs2) would be able to print better test errors out of the box, among other features, but I have no clue if it would work well or at all in our stack (in theory yes, but it's a larger piece of work).
2023-12-05 20:20:54 +00:00
org/clojure/math.combinatorics/0.2.0/math.combinatorics-0.2.0.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
org/clojure/spec.alpha/0.3.218/spec.alpha-0.3.218.jar
Introduce malli library (#17867) This commit is the foundational step to start using malli (https://github.com/metosin/malli) in this project. Take in consideration we will only be able to realize malli's full power in future iterations. For those without context: the mobile team watched a presentation about malli and went through a light RFC to put everyone on the same page, among other discussions here and there in PRs. To keep things relatively short: 1. Unit, integration and component tests will short-circuit (fail) when inputs/outputs don't conform to their respective function schemas (CI should fail too). 2. Failed schema checks will not block the app from initializing, nor throw an exception that would trigger the LogBox. Exceptions are only thrown in the scope of automated tests. 3. There's zero performance impact in production code because we only instrument. Instrumentation is removed from the compiled code due to the usage of "^boolean js.goog/DEBUG". 4. We shouldn't expect any meaningful slowdown during development. **What are we instrumenting in this PR?** Per our team's agreement, we're only instrumenting the bare minimum to showcase 2 examples. - Instrument a utility function utils.money/format-amount using the macro approach. - Instrument a quo component quo.components.counter.step.view/view using the functional approach. Both approaches are useful, the functional approach is powerful and allow us to instrument anonymous functions, like the ones we pass to subscriptions or event handlers, or the higher-order function quo.theme/with-theme. The macro approach is perfect for functions already defined with defn. **I evaluated the schema or function in the REPL but nothing changes** - If you evaluate the source function, you need to evaluate schema/=> or schema/instrument as well. - Remember to *var quote* when using schema/instrument. - You must call "(status-im2.setup.schema/setup!)" after any var is re-instrumented. It's advisable to add a keybinding in your editor to send this expression automatically to the CLJS REPL, or add the call at the end of the namespace you are working on (similar to how some devs add "(run-tests)" at the end of test namespaces). **Where should schemas be defined?** For the moment, we should focus on instrumenting quo components, so define each function schema in the same namespace as the component's public "view" var. To be specific: - A schema used only to instrument a single function and not used elsewhere, like a quo component schema, wouldn't benefit from being defined in a separate namespace because that would force the developer to constantly open two files instead of one to check function signatures. - A common schema reused across the repo, like ":schema.common/theme" should be registered in the global registry "schema.registry" so that consumers can just refer to it by keyword, as if it was a built-in malli schema. - A common schema describing status-go entities like message, notification, community, etc can be stored either in the respective "src/status_im2/contexts/*" or registered globally, or even somewhere else. This is yet to be defined, but since I chose not to include schemas for them, we can postpone this guideline.
2023-11-18 14:04:48 +00:00
org/clojure/test.check/1.1.1/test.check-1.1.1.jar
Add Promesa to simplify working with promises (#18767) * added promesa (clj) Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> * ref(resize): using promesa instead of passing cb Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> --------- Signed-off-by: Cristian Lungu <lungucristian95@gmail.com>
2024-03-04 11:59:52 +00:00
org/clojure/tools.analyzer/1.1.0/tools.analyzer-1.1.0.jar
Upgrade clj-kondo to 2024.03.13 (#19930) This PR upgrades clj-kondo (our Clojure linter) from v2023-09-07 to v2024-03-13, so ~6 months of development updates. You can check out the changes starting at https://github.com/clj-kondo/clj-kondo/blob/master/CHANGELOG.md#20231020. Nothing terribly useful to us this time, but as usual, clj-kondo can catch more problems and more reliably than before.
2024-05-09 15:04:31 +00:00
org/clojure/tools.analyzer.jvm/1.2.2/tools.analyzer.jvm-1.2.2.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
org/clojure/tools.cli/1.0.206/tools.cli-1.0.206.jar
dx(debug)_: Add FlowStorm, a tracing debugger for Clojure(Script) (#20054) Adds FlowStorm https://github.com/flow-storm/flow-storm-debugger v3.7.5, a well known (tracing) debugger for Clojure(Script). With FlowStorm, you can debug almost any cljs function in status-mobile. And although it is not as capable as on the JVM, its main features work well enough. How do I use it? Please, check the markdown diff in this PR: doc/debugging.md. When would you use FlowStorm in status-mobile? You can use it all the time if you want, but FlowStorm can be a powerful tool to understand complex pieces of code. Consider those large subscriptions or event handlers. Or all those components with lots of bindings and calculations. Understanding some of these things is no easy task, even with a REPL. It is not a replacement for re-frisk, those are very different tools and each have their place. Resources: - Repository: https://github.com/flow-storm/flow-storm-debugger - Documentation: https://flow-storm.github.io/flow-storm-debugger - Features: https://github.com/flow-storm/flow-storm-debugger#features - YouTube demos: https://github.com/flow-storm/flow-storm-debugger#some-demo-videos-newers-at-the-top
2024-06-03 22:47:10 +00:00
org/clojure/tools.deps/0.17.1297/tools.deps-0.17.1297.jar
org/clojure/tools.gitlibs/2.5.190/tools.gitlibs-2.5.190.jar
Upgrade re-frame to latest (#19931) Upgrade re-frame to latest, from v1.3.0 (released on 2022-08-27) to latest v1.4.3 (released on 2024-01-25). Important changes: - [Added] re-frame.alpha namespace, for testing proposed features (see flows (https://github.com/day8/re-frame/discussions/795) and polymorphic subscriptions https://github.com/day8/re-frame/issues/680#issuecomment-1676487563). - [Added] dispatch-sync now emits a :sync trace to indicate when it has finished. - Re-frame upgraded its dependency on Reagent to latest v1.2.0. - There are two breaking changes in v1.4.0, but they don't affect us because we don't use interceptors path and unwrap.
2024-05-14 00:18:16 +00:00
org/clojure/tools.logging/1.2.4/tools.logging-1.2.4.jar
hot reload and re-frisk 1.3.1 Signed-off-by: Andrey Shovkoplyas <motor4ik@gmail.com>
2020-05-03 14:14:02 +00:00
org/clojure/tools.macro/0.1.5/tools.macro-0.1.5.jar
dx(debug)_: Add FlowStorm, a tracing debugger for Clojure(Script) (#20054) Adds FlowStorm https://github.com/flow-storm/flow-storm-debugger v3.7.5, a well known (tracing) debugger for Clojure(Script). With FlowStorm, you can debug almost any cljs function in status-mobile. And although it is not as capable as on the JVM, its main features work well enough. How do I use it? Please, check the markdown diff in this PR: doc/debugging.md. When would you use FlowStorm in status-mobile? You can use it all the time if you want, but FlowStorm can be a powerful tool to understand complex pieces of code. Consider those large subscriptions or event handlers. Or all those components with lots of bindings and calculations. Understanding some of these things is no easy task, even with a REPL. It is not a replacement for re-frisk, those are very different tools and each have their place. Resources: - Repository: https://github.com/flow-storm/flow-storm-debugger - Documentation: https://flow-storm.github.io/flow-storm-debugger - Features: https://github.com/flow-storm/flow-storm-debugger#features - YouTube demos: https://github.com/flow-storm/flow-storm-debugger#some-demo-videos-newers-at-the-top
2024-06-03 22:47:10 +00:00
org/clojure/tools.namespace/1.4.4/tools.namespace-1.4.4.jar
Add Promesa to simplify working with promises (#18767) * added promesa (clj) Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> * ref(resize): using promesa instead of passing cb Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> --------- Signed-off-by: Cristian Lungu <lungucristian95@gmail.com>
2024-03-04 11:59:52 +00:00
org/clojure/tools.reader/1.3.7/tools.reader-1.3.7.jar
dx(debug)_: Add FlowStorm, a tracing debugger for Clojure(Script) (#20054) Adds FlowStorm https://github.com/flow-storm/flow-storm-debugger v3.7.5, a well known (tracing) debugger for Clojure(Script). With FlowStorm, you can debug almost any cljs function in status-mobile. And although it is not as capable as on the JVM, its main features work well enough. How do I use it? Please, check the markdown diff in this PR: doc/debugging.md. When would you use FlowStorm in status-mobile? You can use it all the time if you want, but FlowStorm can be a powerful tool to understand complex pieces of code. Consider those large subscriptions or event handlers. Or all those components with lots of bindings and calculations. Understanding some of these things is no easy task, even with a REPL. It is not a replacement for re-frisk, those are very different tools and each have their place. Resources: - Repository: https://github.com/flow-storm/flow-storm-debugger - Documentation: https://flow-storm.github.io/flow-storm-debugger - Features: https://github.com/flow-storm/flow-storm-debugger#features - YouTube demos: https://github.com/flow-storm/flow-storm-debugger#some-demo-videos-newers-at-the-top
2024-06-03 22:47:10 +00:00
org/codehaus/plexus/plexus-cipher/2.0/plexus-cipher-2.0.jar
org/codehaus/plexus/plexus-classworlds/2.6.0/plexus-classworlds-2.6.0.jar
org/codehaus/plexus/plexus-component-annotations/2.1.0/plexus-component-annotations-2.1.0.jar
org/codehaus/plexus/plexus-interpolation/1.26/plexus-interpolation-1.26.jar
org/codehaus/plexus/plexus-sec-dispatcher/2.0/plexus-sec-dispatcher-2.0.jar
org/codehaus/plexus/plexus-utils/3.3.1/plexus-utils-3.3.1.jar
org/eclipse/jetty/jetty-client/9.4.48.v20220622/jetty-client-9.4.48.v20220622.jar
org/eclipse/jetty/jetty-http/9.4.48.v20220622/jetty-http-9.4.48.v20220622.jar
org/eclipse/jetty/jetty-io/9.4.48.v20220622/jetty-io-9.4.48.v20220622.jar
org/eclipse/jetty/jetty-util/9.4.48.v20220622/jetty-util-9.4.48.v20220622.jar
org/eclipse/sisu/org.eclipse.sisu.inject/0.3.5/org.eclipse.sisu.inject-0.3.5.jar
org/eclipse/sisu/org.eclipse.sisu.plexus/0.3.5/org.eclipse.sisu.plexus-0.3.5.jar
use shadow-cljs Signed-off-by: Jakub Sokołowski <jakub@status.im> Signed-off-by: yenda <eric@status.im>
2019-09-07 12:57:22 +00:00
org/javassist/javassist/3.18.1-GA/javassist-3.18.1-GA.jar
dx(debug)_: Add FlowStorm, a tracing debugger for Clojure(Script) (#20054) Adds FlowStorm https://github.com/flow-storm/flow-storm-debugger v3.7.5, a well known (tracing) debugger for Clojure(Script). With FlowStorm, you can debug almost any cljs function in status-mobile. And although it is not as capable as on the JVM, its main features work well enough. How do I use it? Please, check the markdown diff in this PR: doc/debugging.md. When would you use FlowStorm in status-mobile? You can use it all the time if you want, but FlowStorm can be a powerful tool to understand complex pieces of code. Consider those large subscriptions or event handlers. Or all those components with lots of bindings and calculations. Understanding some of these things is no easy task, even with a REPL. It is not a replacement for re-frisk, those are very different tools and each have their place. Resources: - Repository: https://github.com/flow-storm/flow-storm-debugger - Documentation: https://flow-storm.github.io/flow-storm-debugger - Features: https://github.com/flow-storm/flow-storm-debugger#features - YouTube demos: https://github.com/flow-storm/flow-storm-debugger#some-demo-videos-newers-at-the-top
2024-06-03 22:47:10 +00:00
org/java-websocket/Java-WebSocket/1.5.3/Java-WebSocket-1.5.3.jar
Add Promesa to simplify working with promises (#18767) * added promesa (clj) Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> * ref(resize): using promesa instead of passing cb Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> --------- Signed-off-by: Cristian Lungu <lungucristian95@gmail.com>
2024-03-04 11:59:52 +00:00
org/jboss/logging/jboss-logging/3.4.3.Final/jboss-logging-3.4.3.Final.jar
org/jboss/threads/jboss-threads/3.5.0.Final/jboss-threads-3.5.0.Final.jar
org/jboss/xnio/xnio-api/3.8.8.Final/xnio-api-3.8.8.Final.jar
org/jboss/xnio/xnio-nio/3.8.8.Final/xnio-nio-3.8.8.Final.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
org/jspecify/jspecify/0.2.0/jspecify-0.2.0.jar
use shadow-cljs Signed-off-by: Jakub Sokołowski <jakub@status.im> Signed-off-by: yenda <eric@status.im>
2019-09-07 12:57:22 +00:00
org/msgpack/msgpack/0.6.12/msgpack-0.6.12.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
org/ow2/asm/asm/9.4/asm-9.4.jar
dx(debug)_: Add FlowStorm, a tracing debugger for Clojure(Script) (#20054) Adds FlowStorm https://github.com/flow-storm/flow-storm-debugger v3.7.5, a well known (tracing) debugger for Clojure(Script). With FlowStorm, you can debug almost any cljs function in status-mobile. And although it is not as capable as on the JVM, its main features work well enough. How do I use it? Please, check the markdown diff in this PR: doc/debugging.md. When would you use FlowStorm in status-mobile? You can use it all the time if you want, but FlowStorm can be a powerful tool to understand complex pieces of code. Consider those large subscriptions or event handlers. Or all those components with lots of bindings and calculations. Understanding some of these things is no easy task, even with a REPL. It is not a replacement for re-frisk, those are very different tools and each have their place. Resources: - Repository: https://github.com/flow-storm/flow-storm-debugger - Documentation: https://flow-storm.github.io/flow-storm-debugger - Features: https://github.com/flow-storm/flow-storm-debugger#features - YouTube demos: https://github.com/flow-storm/flow-storm-debugger#some-demo-videos-newers-at-the-top
2024-06-03 22:47:10 +00:00
org/slf4j/jcl-over-slf4j/1.7.36/jcl-over-slf4j-1.7.36.jar
Add Promesa to simplify working with promises (#18767) * added promesa (clj) Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> * ref(resize): using promesa instead of passing cb Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> --------- Signed-off-by: Cristian Lungu <lungucristian95@gmail.com>
2024-03-04 11:59:52 +00:00
org/slf4j/slf4j-api/2.0.9/slf4j-api-2.0.9.jar
org/slf4j/slf4j-nop/2.0.9/slf4j-nop-2.0.9.jar
use shadow-cljs Signed-off-by: Jakub Sokołowski <jakub@status.im> Signed-off-by: yenda <eric@status.im>
2019-09-07 12:57:22 +00:00
org/wildfly/client/wildfly-client-config/1.0.1.Final/wildfly-client-config-1.0.1.Final.jar
Add Promesa to simplify working with promises (#18767) * added promesa (clj) Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> * ref(resize): using promesa instead of passing cb Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> --------- Signed-off-by: Cristian Lungu <lungucristian95@gmail.com>
2024-03-04 11:59:52 +00:00
org/wildfly/common/wildfly-common/1.5.4.Final/wildfly-common-1.5.4.Final.jar
Add universal QR scanner via common router Rename events Add router to handle all links Use router in add new chat Unify universal link and universal qr with router Add icon for universal scanner Update tests Now routing is tested in routing PR lint Cleanup QA fixes Scan own profile Handle more EIP Fix wallet scanner Fix stack for view profile in UL Signed-off-by: Gheorghe Pinzaru <feross95@gmail.com>
2020-07-30 09:39:55 +00:00
prismatic/schema/1.1.7/schema-1.1.7.jar
Upgrade clj-kondo to 2024.03.13 (#19930) This PR upgrades clj-kondo (our Clojure linter) from v2023-09-07 to v2024-03-13, so ~6 months of development updates. You can check out the changes starting at https://github.com/clj-kondo/clj-kondo/blob/master/CHANGELOG.md#20231020. Nothing terribly useful to us this time, but as usual, clj-kondo can catch more problems and more reliably than before.
2024-05-09 15:04:31 +00:00
reagent/reagent/1.2.0/reagent-1.2.0.jar
hot reload and re-frisk 1.3.1 Signed-off-by: Andrey Shovkoplyas <motor4ik@gmail.com>
2020-05-03 14:14:02 +00:00
re-com/re-com/2.8.0/re-com-2.8.0.jar
Upgrade clj-kondo to 2024.03.13 (#19930) This PR upgrades clj-kondo (our Clojure linter) from v2023-09-07 to v2024-03-13, so ~6 months of development updates. You can check out the changes starting at https://github.com/clj-kondo/clj-kondo/blob/master/CHANGELOG.md#20231020. Nothing terribly useful to us this time, but as usual, clj-kondo can catch more problems and more reliably than before.
2024-05-09 15:04:31 +00:00
refactor-nrepl/refactor-nrepl/3.9.1/refactor-nrepl-3.9.1.jar
Upgrade re-frame to latest (#19931) Upgrade re-frame to latest, from v1.3.0 (released on 2022-08-27) to latest v1.4.3 (released on 2024-01-25). Important changes: - [Added] re-frame.alpha namespace, for testing proposed features (see flows (https://github.com/day8/re-frame/discussions/795) and polymorphic subscriptions https://github.com/day8/re-frame/issues/680#issuecomment-1676487563). - [Added] dispatch-sync now emits a :sync trace to indicate when it has finished. - Re-frame upgraded its dependency on Reagent to latest v1.2.0. - There are two breaking changes in v1.4.0, but they don't affect us because we don't use interceptors path and unwrap.
2024-05-14 00:18:16 +00:00
re-frame/re-frame/1.4.3/re-frame-1.4.3.jar
Switcher and Bottom Tabs Animations and UI Performance Improvements - Migrated Switcher animations to Reanimated V2 - Added bottom tabs & Stacks Animations - Improved bottom tabs, tab changing performance - Polished android & IOS UI
2022-06-28 17:27:21 +00:00
re-frisk-remote/re-frisk-remote/1.6.0/re-frisk-remote-1.6.0.jar
hot reload and re-frisk 1.3.1 Signed-off-by: Andrey Shovkoplyas <motor4ik@gmail.com>
2020-05-03 14:14:02 +00:00
re-frisk/sente/1.15.0/sente-1.15.0.jar
ring-cors/ring-cors/0.1.8/ring-cors-0.1.8.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
ring/ring-codec/1.2.0/ring-codec-1.2.0.jar
ring/ring-core/1.9.6/ring-core-1.9.6.jar
nix: update clojure dependencies Signed-off-by: Jakub Sokołowski <jakub@status.im> Signed-off-by: andrey <motor4ik@gmail.com>
2021-03-01 11:49:03 +00:00
thheller/shadow-client/1.3.3/shadow-client-1.3.3.jar
Add Promesa to simplify working with promises (#18767) * added promesa (clj) Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> * ref(resize): using promesa instead of passing cb Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> --------- Signed-off-by: Cristian Lungu <lungucristian95@gmail.com>
2024-03-04 11:59:52 +00:00
thheller/shadow-cljs/2.26.2/shadow-cljs-2.26.2-aot.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
thheller/shadow-cljsjs/0.0.22/shadow-cljsjs-0.0.22.jar
Add Promesa to simplify working with promises (#18767) * added promesa (clj) Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> * ref(resize): using promesa instead of passing cb Signed-off-by: Cristian Lungu <lungucristian95@gmail.com> --------- Signed-off-by: Cristian Lungu <lungucristian95@gmail.com>
2024-03-04 11:59:52 +00:00
thheller/shadow-undertow/0.3.3/shadow-undertow-0.3.3.jar
use shadow-cljs Signed-off-by: Jakub Sokołowski <jakub@status.im> Signed-off-by: yenda <eric@status.im>
2019-09-07 12:57:22 +00:00
thheller/shadow-util/0.7.0/shadow-util-0.7.0.jar
Add custom linter for i18n/label translation keywords (#17610) This commit adds a custom linter to verify i18n/label is called with a qualified keyword, like :t/foo. More sophisticated linters are possible too. We also set the stage for other developers to consider more lint automation instead of manually reviewing conventions in PRs. If you want to understand how to write custom linters, check out https://github.com/clj-kondo/clj-kondo/blob/master/doc/hooks.md. You can fire the Clojure JVM REPL in status-mobile and play with the clj-kondo hook too, it works beautifully. Why do we care? By making sure all translation keywords are qualified with "t", it is trivial to grep or replace them because they're unique in the repo, and can't be confused with other words if you search by ":t/<something>". Note: It's a best practice to commit clj-kondo configuration from external libraries in the .clj-kondo directory. The directory .clj-kondo/babashka is auto-generated, that's why it was added.
2023-10-11 21:53:34 +00:00
tigris/tigris/0.1.2/tigris-0.1.2.jar