Use commentron instead of Comment SDK calls #1149

Merged
kekkyojin merged 2 commits from interacting-comment-servers into master 2021-02-24 16:23:34 +01:00
Showing only changes of commit 20579eff12 - Show all commits

View file

@ -65,7 +65,7 @@ public class Comments {
akinwale commented 2021-02-24 13:21:51 +01:00 (Migrated from github.com)
Review

I think you can just use the current timestamp as the id here. Although we're not tracing request JSON RPC request IDs at the moment, we may want to in the future.

I think you can just use the current timestamp as the id here. Although we're not tracing request JSON RPC request IDs at the moment, we may want to in the future.
kekkyojin commented 2021-02-24 14:59:20 +01:00 (Migrated from github.com)
Review

Changed in the new commit

Changed in the new commit
akinwale commented 2021-02-24 13:21:51 +01:00 (Migrated from github.com)
Review

I think you can just use the current timestamp as the id here. Although we're not tracing request JSON RPC request IDs at the moment, we may want to in the future.

I think you can just use the current timestamp as the id here. Although we're not tracing request JSON RPC request IDs at the moment, we may want to in the future.
kekkyojin commented 2021-02-24 14:59:20 +01:00 (Migrated from github.com)
Review

Changed in the new commit

Changed in the new commit
Map<String, Object> requestParams = new HashMap<>(4);
requestParams.put("jsonrpc", "2.0");
requestParams.put("id",1);
akinwale commented 2021-02-24 13:21:51 +01:00 (Migrated from github.com)
Review

I think you can just use the current timestamp as the id here. Although we're not tracing request JSON RPC request IDs at the moment, we may want to in the future.

I think you can just use the current timestamp as the id here. Although we're not tracing request JSON RPC request IDs at the moment, we may want to in the future.
kekkyojin commented 2021-02-24 14:59:20 +01:00 (Migrated from github.com)
Review

Changed in the new commit

Changed in the new commit
requestParams.put("id", TimeUnit.MILLISECONDS.toSeconds(System.currentTimeMillis()));
akinwale commented 2021-02-24 13:21:51 +01:00 (Migrated from github.com)
Review

I think you can just use the current timestamp as the id here. Although we're not tracing request JSON RPC request IDs at the moment, we may want to in the future.

I think you can just use the current timestamp as the id here. Although we're not tracing request JSON RPC request IDs at the moment, we may want to in the future.
kekkyojin commented 2021-02-24 14:59:20 +01:00 (Migrated from github.com)
Review

Changed in the new commit

Changed in the new commit
requestParams.put("method", method);
requestParams.put("params", params);

akinwale commented 2021-02-24 13:21:51 +01:00 (Migrated from github.com)
Review

I think you can just use the current timestamp as the id here. Although we're not tracing request JSON RPC request IDs at the moment, we may want to in the future.

I think you can just use the current timestamp as the id here. Although we're not tracing request JSON RPC request IDs at the moment, we may want to in the future.
kekkyojin commented 2021-02-24 14:59:20 +01:00 (Migrated from github.com)
Review

Changed in the new commit

Changed in the new commit
akinwale commented 2021-02-24 13:21:51 +01:00 (Migrated from github.com)
Review

I think you can just use the current timestamp as the id here. Although we're not tracing request JSON RPC request IDs at the moment, we may want to in the future.

I think you can just use the current timestamp as the id here. Although we're not tracing request JSON RPC request IDs at the moment, we may want to in the future.
kekkyojin commented 2021-02-24 14:59:20 +01:00 (Migrated from github.com)
Review

Changed in the new commit

Changed in the new commit