profile
viewpoint

odysseyscience/react-s3-uploader 689

React component that renders an <input type="file"/> and automatically uploads to an S3 bucket

seanadkinson/react-pdx-react-router 4

Code used for react-router presentation at React PDX on Feb 10, 2015

seanadkinson/react-chartjs 3

common react charting components using chart.js

seanadkinson/Ektorp 1

Java API for CouchDB

seanadkinson/ektorplucene 1

Addon for Ektorp (ekorp.org) that enables searching couchdb with couchdb-lucene

seanadkinson/less.js 1

Leaner CSS, in your browser.

seanadkinson/pdxjs-webpack-examples 1

Examples used when speaking at PDX JS on Wednesday, September 24th, 2014.

seanadkinson/swagger-ui 1

Swagger UI is a dependency-free collection of HTML, Javascript, and CSS assets that dynamically generate beautiful documentation from a Swagger-compliant API.

seanadkinson/beeswithmachineguns 0

A utility for arming (creating) many bees (micro EC2 instances) to attack (load test) targets (web applications).

issue closedstreem/react-native-select-contact

i have error like this with react-native-select-contact

FAILURE: Build failed with an exception.

  • What went wrong: Could not determine the dependencies of task ':app:mergeDebugAssets'.

Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'. Could not resolve project :react-native-select-contact. Required by: project :app Unable to find a matching configuration of project :react-native-select-contact: - None of the consumable configurations have attributes.

  • Try: Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

  • Get more help at https://help.gradle.org

BUILD FAILED in 5s

at makeError (/Users/apple/Desktop/workspace/react_native/EzyRent/node_modules/execa/index.js:174:9)
at /Users/apple/Desktop/workspace/react_native/EzyRent/node_modules/execa/index.js:278:16
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async runOnAllDevices (/Users/apple/Desktop/workspace/react_native/EzyRent/node_modules/@react-native-community/cli-platform-android/build/commands/runAndroid/runOnAllDevices.js:94:5)
at async Command.handleAction (/Users/apple/Desktop/workspace/react_native/EzyRent/node_modules/@react-native-community/cli/build/index.js:186:9)

closed time in a day

prakashsaran

issue commentstreem/react-native-select-contact

i have error like this with react-native-select-contact

Published v1.5.0 after merging that PR. Thanks!

prakashsaran

comment created time in a day

created tagstreem/react-native-select-contact

tagv1.5.0

A cross-platform contact selection library for react-native

created time in a day

push eventstreem/react-native-select-contact

Sean Adkinson

commit sha 4485fd612a86cbbf633ded282598e971632cb14a

1.4.0 changelog

view details

Sean Adkinson

commit sha 4d28f9cd4c43f16a7ddbab6ee82d2bb96452e377

1.4.0

view details

Sean Adkinson

commit sha dd1f12b42b764f5c8a4f9f76a4808096a72480b2

Merge branch 'master' of github.com:streem/react-native-select-contact * 'master' of github.com:streem/react-native-select-contact: move files from app folder fix build.gradle update manifest update manifest add application id update android files Update build.gradle

view details

push time in a day

issue closedstreem/react-native-select-contact

[Android] App won't build with RN v0.62.0

Using react-native-select-contact with RN 0.62 causes a build error on Android. I can reproduce this with version 1.2.1+ (didn't try any of the older versions).

Working on a PR to fix. (I already have a working fork here).

closed time in a day

bell-steven

pull request commentstreem/react-native-select-contact

Fix android build error on RN 0.62.0

Will release as v1.5.0

bell-steven

comment created time in a day

push eventstreem/react-native-select-contact

Steven Bell

commit sha 7593d48d97d5089e1011c5dcdf2a000e2f097a4a

Update build.gradle

view details

Steven Bell

commit sha 1f6ee7e6b677a42dd2fafe0a9feda54fdea50a62

update android files

view details

Steven Bell

commit sha 1b458380bc4e43f49e132714a9f8dfa14498abb1

add application id

view details

Steven Bell

commit sha ce6b3f4f0a01bf2d5d9e93dc0d952d3a64ec6a64

update manifest

view details

Steven Bell

commit sha 52c437a58b486cc70f8d5ebcbd38e9064b6ee767

update manifest

view details

Steven Bell

commit sha 9e7b1c782ca3a61aeb373f717d79e8691da57aa5

fix build.gradle

view details

Steven Bell

commit sha 1594509d0cf316d16fbc2deef4c0a3423ab39e9d

move files from app folder

view details

seanadkinson

commit sha 979fb3d5b616f2f6156c9fd09308e2f965d482a0

Merge pull request #27 from bell-steven/revampAndroidFiles Fix android build error on RN 0.62.0

view details

push time in a day

PR merged streem/react-native-select-contact

Fix android build error on RN 0.62.0

Closes #26.

Also, includes most of the changes from #21 and #22.

+131 -246

3 comments

19 changed files

bell-steven

pr closed time in a day

Pull request review commentstreem/react-native-select-contact

Fix android build error on RN 0.62.0

-# Add project specific ProGuard rules here.-# By default, the flags in this file are appended to flags specified-# in /usr/local/Cellar/android-sdk/24.3.3/tools/proguard/proguard-android.txt-# You can edit the include path and order by changing the proguardFiles-# directive in build.gradle.-#-# For more details, see-#   http://developer.android.com/guide/developing/tools/proguard.html--# Add any project specific keep options here:--# If your project uses WebView with JS, uncomment the following-# and specify the fully qualified class name to the JavaScript interface-# class:-#-keepclassmembers class fqcn.of.javascript.interface.for.webview {-#   public *;-#}--# Disabling obfuscation is useful if you collect stack traces from production crashes-# (unless you are using a system that supports de-obfuscate the stack traces).--dontobfuscate--# React Native

Looks like this file was just the same as what RN supplies out of the box, so it wasn't actually doing anything specific to this library.

bell-steven

comment created time in a day

issue commentstreem/react-native-select-contact

i have error like this with react-native-select-contact

Yes, if you can help review and verify fixes, I can merge and publish. Happy to look into making you a maintainer as well, if interested.

prakashsaran

comment created time in a day

pull request commentstreem/react-native-select-contact

[ios] Multi-layer modals support

Published v1.4.0

oxyii

comment created time in a day

created tagstreem/react-native-select-contact

tagv1.4.0

A cross-platform contact selection library for react-native

created time in a day

push eventstreem/react-native-select-contact

Ruslan Baybekov

commit sha 8c41958ec23c541ac6af18b942528e23052d60bf

Milti-layer modals support

view details

seanadkinson

commit sha 278606a503ee287efbf4465f2aeb0faf20fdf3ba

Merge pull request #30 from oxyii/patch-1 [ios] Multi-layer modals support

view details

push time in a day

PR merged streem/react-native-select-contact

[ios] Multi-layer modals support

original: https://github.com/wix/react-native-navigation/blob/c7509c52fab7142b2bffc5b851747ef14b595ef1/lib/ios/RNNModalManager.m#L147-L150

ref #18

+3 -6

2 comments

1 changed file

oxyii

pr closed time in a day

pull request commentstreem/react-native-select-contact

[ios] Multi-layer modals support

👍

oxyii

comment created time in a day

issue commentstreem/react-native-select-contact

i have error like this with react-native-select-contact

@prakashsaran or @lgenzelis , does PR #27 fix this issue for you? We don't use this module in-house anymore, so if you can help us determine the fix, I'm happy to merge and publish. Thanks!

prakashsaran

comment created time in 6 days

Pull request review commentstreem/pbandk

WIP: Refactor and improve JSON support

+package pbandk.json++import kotlinx.serialization.json.*+import pbandk.*+import pbandk.wkt.*+import kotlin.Any+import kotlin.reflect.KProperty1++class JsonWireMarshaller(private val jsonConfig: JsonConfig) :+    WireMarshaller {+    private val json: Json =+        Json(+            JsonConfiguration.Stable.copy(+                prettyPrint = true+            )+        )+    private val jsonValueMarshaller = JsonValueMarshaller(jsonConfig)+    private var currentMessage: JsonElement? = null++    fun toJsonString(): String = currentMessage?.let { json.stringify(JsonElementSerializer, it) }.orEmpty()++    fun toJsonElement() = currentMessage ?: error("Must call writeMessage() before toJsonElement()")++    override fun <T : Message> writeMessage(message: T) {+        check(currentMessage == null) { "JsonWireMarshaller can't be reused with multiple messages" }+        currentMessage = when (message) {+            // Wrapper types use the same JSON representation as the wrapped value+            // https://developers.google.com/protocol-buffers/docs/proto3#json+            is DoubleValue -> writeWrapperValue(message, message.value)+            is FloatValue -> writeWrapperValue(message, message.value)+            is Int64Value -> writeWrapperValue(message, message.value)+            is UInt64Value -> writeWrapperValue(message, message.value)+            is Int32Value -> writeWrapperValue(message, message.value)+            is UInt32Value -> writeWrapperValue(message, message.value)+            is BoolValue -> writeWrapperValue(message, message.value)+            is StringValue -> writeWrapperValue(message, message.value)+            is BytesValue -> writeWrapperValue(message, message.value)+            // Other well-known types with special JSON encoding+            is Timestamp -> jsonValueMarshaller.writeString(+                Util.timestampToString(+                    message+                )+            )+            // All other message types+            else -> writeMessageObject(message)+        }+    }++    private fun writeWrapperValue(message: Message, value: Any) =+        jsonValueMarshaller.writeValue(value, message.fieldDescriptors[0].type)++    private fun <T : Message> writeMessageObject(message: T): JsonObject {+        val jsonContent: MutableMap<String, JsonElement> = linkedMapOf()++        for (fd in message.fieldDescriptors) {+            @Suppress("UNCHECKED_CAST")+            val value = (fd.value as KProperty1<T, *>).get(message)++            if (value == null && fd.oneofMember) continue+            if (!fd.oneofMember && !jsonConfig.outputDefaultValues && fd.type.isDefaultValue(value)) continue

Yeah, we previously explicitly allowed total_count to return as 0, which was useful.

garyp

comment created time in 8 days

Pull request review commentstreem/pbandk

WIP: Refactor and improve JSON support

+package pbandk.json++import kotlinx.serialization.json.*+import pbandk.*+import pbandk.wkt.*+import kotlin.Any++private val FieldDescriptor.jsonNames: List<String>+    get() = listOf(+        jsonName ?: name.underscoreToCamelCase(),+        name+    )++class JsonWireUnmarshaller(private val content: JsonElement, private val jsonConfig: JsonConfig) :+    WireUnmarshaller {+    private val jsonValueUnmarshaller = JsonValueUnmarshaller(jsonConfig)++    @Suppress("UNCHECKED_CAST")+    override fun <T : Message> readMessage(+        messageCompanion: Message.Companion<T>,+        fieldFn: (Int, Any) -> Unit+    ): Map<Int, UnknownField> = try {+        if (!content.isNull) {+            readMessageObject(messageCompanion, content, fieldFn)+        }+        emptyMap()+    } catch (e: InvalidProtocolBufferException) {+        throw e+    } catch (e: Exception) {+        throw InvalidProtocolBufferException("unable to read message", e)+    }++    private fun <T : Message> readMessageObject(+        messageCompanion: Message.Companion<T>,+        content: JsonElement,+        fieldFn: (Int, Any) -> Unit+    ) {+        for ((key, jsonValue) in content.jsonObject) {+            val fd = messageCompanion.fieldDescriptors.firstOrNull { key in it.jsonNames }+                ?: if (jsonConfig.ignoreUnknownFieldsInInput) {+                    continue+                } else {+                    throw InvalidProtocolBufferException("Unknown field name and ignoreUnknownFieldsInInput=false: $key")+                }+            if (jsonValue.isNull) continue+            fieldFn(fd.number, jsonValueUnmarshaller.readValue(jsonValue, fd.type))+        }+    }

So much nicer!

garyp

comment created time in 8 days

Pull request review commentstreem/pbandk

WIP: Refactor and improve JSON support

+package pbandk.json++import kotlinx.serialization.json.*+import pbandk.*+import pbandk.wkt.*+import kotlin.Any+import kotlin.reflect.KProperty1++class JsonWireMarshaller(private val jsonConfig: JsonConfig) :+    WireMarshaller {+    private val json: Json =+        Json(+            JsonConfiguration.Stable.copy(+                prettyPrint = true+            )+        )+    private val jsonValueMarshaller = JsonValueMarshaller(jsonConfig)+    private var currentMessage: JsonElement? = null++    fun toJsonString(): String = currentMessage?.let { json.stringify(JsonElementSerializer, it) }.orEmpty()++    fun toJsonElement() = currentMessage ?: error("Must call writeMessage() before toJsonElement()")++    override fun <T : Message> writeMessage(message: T) {+        check(currentMessage == null) { "JsonWireMarshaller can't be reused with multiple messages" }+        currentMessage = when (message) {+            // Wrapper types use the same JSON representation as the wrapped value+            // https://developers.google.com/protocol-buffers/docs/proto3#json+            is DoubleValue -> writeWrapperValue(message, message.value)+            is FloatValue -> writeWrapperValue(message, message.value)+            is Int64Value -> writeWrapperValue(message, message.value)+            is UInt64Value -> writeWrapperValue(message, message.value)+            is Int32Value -> writeWrapperValue(message, message.value)+            is UInt32Value -> writeWrapperValue(message, message.value)+            is BoolValue -> writeWrapperValue(message, message.value)+            is StringValue -> writeWrapperValue(message, message.value)+            is BytesValue -> writeWrapperValue(message, message.value)+            // Other well-known types with special JSON encoding+            is Timestamp -> jsonValueMarshaller.writeString(+                Util.timestampToString(+                    message+                )+            )+            // All other message types+            else -> writeMessageObject(message)+        }+    }++    private fun writeWrapperValue(message: Message, value: Any) =+        jsonValueMarshaller.writeValue(value, message.fieldDescriptors[0].type)++    private fun <T : Message> writeMessageObject(message: T): JsonObject {+        val jsonContent: MutableMap<String, JsonElement> = linkedMapOf()++        for (fd in message.fieldDescriptors) {+            @Suppress("UNCHECKED_CAST")+            val value = (fd.value as KProperty1<T, *>).get(message)++            if (value == null && fd.oneofMember) continue+            if (!fd.oneofMember && !jsonConfig.outputDefaultValues && fd.type.isDefaultValue(value)) continue++            val jsonValue = value?.let { jsonValueMarshaller.writeValue(it, fd.type) } ?: JsonNull+            jsonContent[jsonConfig.getFieldJsonName(fd)] = jsonValue+        }++        return JsonObject(jsonContent)+    }++}++private class JsonValueMarshaller(private val jsonConfig: JsonConfig) {+    fun writeValue(value: Any, type: FieldDescriptor.Type<*>): JsonElement = when (type) {+        FieldDescriptor.Type.Primitive.Double -> writeDouble(value as Double)+        FieldDescriptor.Type.Primitive.Float -> writeFloat(value as Float)+        FieldDescriptor.Type.Primitive.Int64 -> writeNumber64(value as Long)+        FieldDescriptor.Type.Primitive.UInt64 -> writeNumber64(value as Long)+        FieldDescriptor.Type.Primitive.Int32 -> writeNumber32(value as Int)+        FieldDescriptor.Type.Primitive.Fixed64 -> writeNumber64(value as Long)+        FieldDescriptor.Type.Primitive.Fixed32 -> writeNumber32(value as Int)+        FieldDescriptor.Type.Primitive.Bool -> writeBool(value as Boolean)+        FieldDescriptor.Type.Primitive.String -> writeString(value as String)+        FieldDescriptor.Type.Primitive.Bytes -> writeBytes(value as ByteArr)+        FieldDescriptor.Type.Primitive.UInt32 -> writeNumber32(value as Int)+        FieldDescriptor.Type.Primitive.SFixed32 -> writeNumber32(value as Int)+        FieldDescriptor.Type.Primitive.SFixed64 -> writeNumber64(value as Long)+        FieldDescriptor.Type.Primitive.SInt32 -> writeNumber32(value as Int)+        FieldDescriptor.Type.Primitive.SInt64 -> writeNumber64(value as Long)+        is FieldDescriptor.Type.Message -> when (type.messageCompanion) {+            // Wrapper types use the same JSON representation as the wrapped value+            // https://developers.google.com/protocol-buffers/docs/proto3#json+            is DoubleValue.Companion -> writeDouble(value as Double)+            is FloatValue.Companion -> writeFloat(value as Float)+            is Int64Value.Companion -> writeNumber64(value as Long)+            is UInt64Value.Companion -> writeNumber64(value as Long)+            is Int32Value.Companion -> writeNumber32(value as Int)+            is UInt32Value.Companion -> writeNumber32(value as Int)+            is BoolValue.Companion -> writeBool(value as Boolean)+            is StringValue.Companion -> writeString(value as String)+            is BytesValue.Companion -> writeBytes(value as ByteArr)+            // Other well-known types with special JSON encoding+            is Timestamp.Companion -> writeString(+                Util.timestampToString(+                    value as Timestamp+                )+            )+            // All other message types+            else -> writeMessage(value as Message)+        }+        is FieldDescriptor.Type.Enum -> writeEnum(value as Message.Enum)+        is FieldDescriptor.Type.Repeated -> writeRepeated(value as List<*>, type.valueType)+        is FieldDescriptor.Type.Map -> writeMap(value as Map<*, *>, type.keyType, type.valueType)+    }++    fun writeNumber32(value: Int): JsonElement =+        JsonLiteral(value)++    fun writeNumber64(value: Long): JsonElement =+        JsonLiteral(value.toString())++//    fun writeInt32(value: Int): JsonElement = JsonLiteral(value)+//+//    fun writeInt64(value: Long): JsonElement = JsonLiteral(value.toString())+//+//    fun writeUInt32(value: Int): JsonElement = JsonLiteral(value)+//+//    fun writeUInt64(value: Long): JsonElement = JsonLiteral(value.toString())+//+//    fun writeSInt32(value: Int): JsonElement = JsonLiteral(value)+//+//    fun writeSInt64(value: Long): JsonElement = JsonLiteral(value.toString())

Why commented out?

garyp

comment created time in 8 days

Pull request review commentstreem/pbandk

WIP: Refactor and improve JSON support

+package pbandk.json++import pbandk.Message++fun <T: Message> T.jsonMarshal(jsonConfig: JsonConfig = JsonConfig.DEFAULT) =+    JsonWireMarshaller(jsonConfig).also{ it.writeMessage(this) }.toJsonString()++fun <T : Message> Message.Companion<T>.jsonUnmarshal(data: String, jsonConfig: JsonConfig = JsonConfig.DEFAULT): T =+    unmarshal(JsonWireUnmarshaller.fromString(data, jsonConfig))

Nice to put these extensions only once, as opposed to each generated file

garyp

comment created time in 8 days

Pull request review commentstreem/pbandk

WIP: Refactor and improve JSON support

+package pbandk.json++import kotlinx.serialization.json.*+import pbandk.*+import pbandk.wkt.*+import kotlin.Any+import kotlin.reflect.KProperty1++class JsonWireMarshaller(private val jsonConfig: JsonConfig) :+    WireMarshaller {+    private val json: Json =+        Json(+            JsonConfiguration.Stable.copy(+                prettyPrint = true+            )+        )+    private val jsonValueMarshaller = JsonValueMarshaller(jsonConfig)+    private var currentMessage: JsonElement? = null++    fun toJsonString(): String = currentMessage?.let { json.stringify(JsonElementSerializer, it) }.orEmpty()++    fun toJsonElement() = currentMessage ?: error("Must call writeMessage() before toJsonElement()")++    override fun <T : Message> writeMessage(message: T) {+        check(currentMessage == null) { "JsonWireMarshaller can't be reused with multiple messages" }+        currentMessage = when (message) {+            // Wrapper types use the same JSON representation as the wrapped value+            // https://developers.google.com/protocol-buffers/docs/proto3#json+            is DoubleValue -> writeWrapperValue(message, message.value)+            is FloatValue -> writeWrapperValue(message, message.value)+            is Int64Value -> writeWrapperValue(message, message.value)+            is UInt64Value -> writeWrapperValue(message, message.value)+            is Int32Value -> writeWrapperValue(message, message.value)+            is UInt32Value -> writeWrapperValue(message, message.value)+            is BoolValue -> writeWrapperValue(message, message.value)+            is StringValue -> writeWrapperValue(message, message.value)+            is BytesValue -> writeWrapperValue(message, message.value)+            // Other well-known types with special JSON encoding+            is Timestamp -> jsonValueMarshaller.writeString(+                Util.timestampToString(+                    message+                )+            )+            // All other message types+            else -> writeMessageObject(message)+        }+    }++    private fun writeWrapperValue(message: Message, value: Any) =+        jsonValueMarshaller.writeValue(value, message.fieldDescriptors[0].type)++    private fun <T : Message> writeMessageObject(message: T): JsonObject {+        val jsonContent: MutableMap<String, JsonElement> = linkedMapOf()++        for (fd in message.fieldDescriptors) {+            @Suppress("UNCHECKED_CAST")+            val value = (fd.value as KProperty1<T, *>).get(message)++            if (value == null && fd.oneofMember) continue+            if (!fd.oneofMember && !jsonConfig.outputDefaultValues && fd.type.isDefaultValue(value)) continue

Does this mean we won't have empty strings in our response now? 🎉

garyp

comment created time in 8 days

Pull request review commentstreem/streem-www

Updated job descriptions

 <h2 class="text-center">           <div class="profile-lite parallax animate fade">             <img class="avatar" src="img/employees/Dr Flora Tasse_Principal Research Scientist.jpg" alt="" />             <div class="name">Dr. Flora Tasse</div>-            <div class="role">Head of Computer Vision Reasearch</div>

Woops!

jgstreem

comment created time in 15 days

push eventstreem/streem-www

Sean Adkinson

commit sha cc3a2ad561319dcd6f8dafde7181b5cafea22a49

Another title update

view details

push time in a month

push eventstreem/streem-www

Sean Adkinson

commit sha ec66b44906e2c384ce9be0815db054f6b2f16ab5

Update titles

view details

push time in a month

Pull request review commentstreem/streem-sdk-ios

Update README.md to reflect recent changes in the invitation flow

 Inside your `AppDelegate.application(_, handleEventsForBackgroundURLSession:comp Once the user has logged into your app, inform Streem that they are logged in:  ```swift-    Streem.sharedInstance.identify(-        userId: "john",-        expert: false,-        name: "John Smith", -        avatarUrl: "http://..."+    Streem.sharedInstance.login(+            companyCode: "acme-inc", +            email: "john.smith600@gmail.com", +            password: "StreemIsC00l!", +            expert: true, 

@garyp I think we thought that could happen at some point, but now with invites being much easier to provide to customers, and our REST API available if they did need to access protected data, i don't think we'd actually create user accounts with credentials for customers anymore. Even if we did do that in the future, that customer account would almost certainly be configured as such on the backend, and the provided credentials would be enough to determine if they were an expert or not.

Similar to the login/identify discussion, now that we are providing confidential information in order to login, as opposed to just being told who the current user is, I think specifying that they are an expert in the current world is more confusing than it is potentially helpful in the future.

callum-code

comment created time in a month

Pull request review commentstreem/streem-sdk-ios

Update README.md to reflect recent changes in the invitation flow

 Inside your `AppDelegate.application(_, handleEventsForBackgroundURLSession:comp Once the user has logged into your app, inform Streem that they are logged in:  ```swift-    Streem.sharedInstance.identify(-        userId: "john",-        expert: false,-        name: "John Smith", -        avatarUrl: "http://..."+    Streem.sharedInstance.login(+            companyCode: "acme-inc", +            email: "john.smith600@gmail.com", +            password: "StreemIsC00l!", +            expert: true, 

Can we take expert off the API, and hard-code the fact that logging in with username/password means you are an expect?

callum-code

comment created time in a month

push eventstreem/streem-www

Sean Adkinson

commit sha a6a6cd994358170e773d84e3883d9048026ed3a1

Add redirects to build

view details

push time in a month

pull request commentstreem/streem-sdk-ios

Update README.md to reflect recent changes in the invitation flow

Re: @garyp's comment, I completely agree people will come into the SDK with users provisioned in SWAGA, and if we add login(withUsername:andPassword), the API will feel correct.

Note that this PR and repo are public, so sorry for people reading this and not understanding what SWAGA is :-)

callum-code

comment created time in a month

pull request commentstreem/pbandk

Publish library for ServiceGenerator plugins; fix example projects

Even better! :+1:

garyp

comment created time in 2 months

Pull request review commentstreem/pbandk

Publish library for ServiceGenerator plugins; fix example projects

 buildscript {-    ext.kotlin_version = '1.3.11'+    ext.kotlin_serialization_version = '0.20.0'+    ext.pbandk_version = 'master-SNAPSHOT'     repositories {         mavenCentral()     }     dependencies {-        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"-        classpath 'com.google.protobuf:protobuf-gradle-plugin:0.8.7'+        classpath 'org.jetbrains.kotlin:kotlin-gradle-plugin:1.3.72'+        classpath 'org.jetbrains.kotlin:kotlin-serialization:1.3.72'+        classpath 'com.google.protobuf:protobuf-gradle-plugin:0.8.12'     } } +import org.jetbrains.kotlin.gradle.tasks.KotlinCompile+ allprojects {     apply plugin: 'kotlin'      repositories {         mavenCentral()+        maven { url 'https://jitpack.io' }+    }++    dependencies {+        implementation 'org.jetbrains.kotlin:kotlin-stdlib-jdk8'+    }++    tasks.withType(KotlinCompile).configureEach {+        kotlinOptions {+            jvmTarget = '1.8'+        }     } }  project(':application') {+    apply plugin: 'kotlinx-serialization'     apply plugin: 'application'     apply plugin: 'com.google.protobuf'      mainClassName = 'pbandk.examples.greeter.MainKt'     applicationName = 'greeter'      dependencies {-        compile 'com.github.streem.pbandk:pbandk-runtime-jvm:0.8.0'-        compile 'org.jetbrains.kotlinx:kotlinx-coroutines-core:1.1.0'+        implementation "org.jetbrains.kotlinx:kotlinx-serialization-runtime:$kotlin_serialization_version"+        implementation 'org.jetbrains.kotlinx:kotlinx-coroutines-core:1.3.6'+        implementation "com.github.streem.pbandk:pbandk-runtime-jvm:$pbandk_version"

Worth centralizing the other version numbers like you did pbandk_version?

garyp

comment created time in 2 months

Pull request review commentstreem/pbandk

Publish library for ServiceGenerator plugins; fix example projects

 buildscript {-    ext.kotlin_version = '1.3.11'+    ext.kotlin_serialization_version = '0.20.0'+    ext.protobuf_version = '3.11.1'+    ext.pbandk_version = 'master-SNAPSHOT'

You sure you want the snapshot version here?

garyp

comment created time in 2 months

issue commentodysseyscience/react-s3-uploader

index.d.ts missing methods/props

Published v4.9.3, thanks!

mrjones2014

comment created time in 2 months

issue closedodysseyscience/react-s3-uploader

index.d.ts missing methods/props

I have added a PR (216) which adds these to index.d.ts

it was missing scrubFilename prop and the uploadFile method on S3Upload

closed time in 2 months

mrjones2014

push eventodysseyscience/react-s3-uploader

Sean Adkinson

commit sha efa19fbaa2d2db11027f352937c93283a8d7d50f

4.9.3

view details

Sean Adkinson

commit sha eefdc0782d2d3181c9b9f8eea0b9f50f0d2ca81d

Changelot for 4.9.3

view details

push time in 2 months

created tagodysseyscience/react-s3-uploader

tagv4.9.3

React component that renders an <input type="file"/> and automatically uploads to an S3 bucket

created time in 2 months

pull request commentodysseyscience/react-s3-uploader

Add Missing Props and Methods to index.d.ts

@mrjones2014 Thanks, sorry for the delay... will merge

mrjones2014

comment created time in 2 months

push eventodysseyscience/react-s3-uploader

Mat Jones

commit sha e39de72a0173fce4d3ac9a56aafb6bb111178429

Update index.d.ts add missing methods and props to index.d.ts

view details

Mat Jones

commit sha be59d696a14b55978b5a2ccff8ef98edf5ed6799

Merge pull request #1 from mrjones2014/mrjones2014-patch-1 Update index.d.ts

view details

seanadkinson

commit sha ecdb250d36da0d0d55796731bdb4ea46ff11fa62

Merge pull request #216 from mrjones2014/master Add Missing Props and Methods to index.d.ts

view details

push time in 2 months

PR merged odysseyscience/react-s3-uploader

Add Missing Props and Methods to index.d.ts

index.d.ts was missing one of the props for the component, and missing the uploadFile method from the S3Upload class.

+3 -1

2 comments

1 changed file

mrjones2014

pr closed time in 2 months

Pull request review commentstreem/streem-sdk-ios

Enhanced documentation

 Example Streem SDK project for IOS * Cocoapods 1.6 or later * ARKit compatible device with IOS 12 or later -## Streem Functions--| Core Functionality                                | Streem App        | SDK Status        |-| ------------------------------------------------- | ----------------- | ----------------- |-| Non-AR remote streeming                           | ✅ 				| ✅                |-| Non-AR onsite streeming                           | ✅ 				| ✅                |-| Pro-to-Pro calling                                | ❌ 				| ✅                |-| Pro CallKit integration                           | ✅ 				| ✅                |-| Customer CallKit integration                      | ❌ 				| ✅                |-| Laser tool                                        | ✅ 				| ✅                |-| Landscape Support                                 | ❌ 				| ✅                |-| iPad Support                                      | ✅ 				| ✅                |-| API Access (GET /streems)                         | ❌ 				| ✅                |-| AR Remote Streem                                  | ✅ 				| ✅                |-| AR Onsite Streem                                  | ✅ 				| ✅                |-| AR Arrow Tool                                     | ✅ 				| ✅                |-| Remote Streemshot                                 | ✅ 				| ✅                |-| Onsite Streemshot                           	    | ✅ 				| ✅                |-| Streemshot Editing                                | ✅					| ✅                    |-| Streemshot Processing                             | ✅					|                   |-| Onsite Recording                           	    | ✅ 				| ✅                |-| Remote Recording                                  | ✅ 				|                   |-- ### Company/App Setup  * Obtain your `company_id` from Streem * Provide your IOS bundle id for any apps you are going to use the Streem SDK in (later you will be able to do this from a self-service portal) * Streem will provide you with an `appId` and `appSecret` for each of your IOS apps * Now that you have your App IDs, follow the steps in the [CallKit Setup Instructions](docs/callkit.md)+* The StreemKit SDK requires a navigation controller for streems. Please make sure your entry point to the StreemKit SDK is in a `NavigationController`  ### Installation  Currently Streem supports Cocoapods installation (Carthage, Swift Package Manager, and Manual to come later) -Add a `source` to your `Podfile`:+Have Streem add you to their cocoapods repository, and then add a `source` to your `Podfile`:

We can see what it would take, but cocoapods may not work well with a private repo. Instead, we can limit the ability to use by who gets App ID/Secrets. If Ty wants to restrict that, then we should add a feature flag for whether that shows up in admin.

zach-babb-streem

comment created time in 2 months

Pull request review commentstreem/streem-sdk-ios

Enhanced documentation

 If CallKit has been set up correctly, Tom's device will ring like a phone call,  Note: Due to an issue with ARKit, you cannot start a Remote Streem from a view using the camera https://forums.developer.apple.com/message/411888#411888 +#### Roles++Roles dictate which side of the streem your on as in whether you're sharing your video or receiving video. They also affect which tools are available to you. The different roles are:++* `LOCAL_CUSTOMER`: This is the primary role for the customer in a two-way streem+* `ONSITE_CUSTOMER`: This is the primary role for a customer in an onsite (one-way) streem 

I dont think ONSITE_CUSTOMER exists, does it?

zach-babb-streem

comment created time in 2 months

Pull request review commentstreem/streem-sdk-ios

Enhanced documentation

 If CallKit has been set up correctly, Tom's device will ring like a phone call,  Note: Due to an issue with ARKit, you cannot start a Remote Streem from a view using the camera https://forums.developer.apple.com/message/411888#411888 +#### Roles++Roles dictate which side of the streem your on as in whether you're sharing your video or receiving video. They also affect which tools are available to you. The different roles are:++* `LOCAL_CUSTOMER`: This is the primary role for the customer in a two-way streem+* `ONSITE_CUSTOMER`: This is the primary role for a customer in an onsite (one-way) streem +* `REMOTE_PRO`: This is the primary role for the pro in a two-way streem+* `ONSITE_PRO`: This is the primary role for a pro in an onsite (one-way) streem++In general if you are starting a remote streem you will want the `LOCAL_CUSTOMER` role. ++### Getting Remote User IDs++In order to start a remote streem, your app will need to supply the `remoteUserId` of the user your app's user is going to streem with. There are two mechanisms available in the SDK for retrieving a `remoteUserId`. The first is through getting a list of recently logged in users. The second is through an invitation. In addition to these two methods, you can maintain your own list of `remoteUserIds` and supply them to your app however you choose. ++#### Recently Logged In Users++By calling the SDK's `getRecentlyIdentifiedUsers` method on the Streem `sharedInstance` you will receive a list of recently logged in users for your company. You can use this method to filter only experts. You then give this method a callback where you select the remote user through some mechanism and start the streem. 

We didn't really discuss, but I don't have a burning desire say we can't support this method. It's not like this would be particularly useful in a production deployment, so its existence it illustrate functionality in a quick way, without the need for the customer to create integrations with their database, seems okay.

zach-babb-streem

comment created time in 2 months

pull request commentstreem/react-native-select-contact

Fix android build error on RN 0.62.0

Thanks guys... @garyp, would you be able to take a quick look? I'll release if gtg

bell-steven

comment created time in 2 months

MemberEvent
more