You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, in iOS and Java, the library will compile differently in each case, so it's a compile time error to use the push-receiving methods if on OS X or non-Android Java. But we could have a method/constant/something to determine it programatically at runtime, specially given we're adding push-receiving support for browsers (JS).
My proposal would be rest.push.canActivate() -> Bool. If it returns true, then the rest.push.activate method exists.
Alternative names: canReceive, canRegister. The former might be misleading since maybe it can't receive for case-specific reasons even if the platform is able to (e. g. the user didn't give permission); the latter is more precise but it lacks consistency with the activate method.
Right now, in iOS and Java, the library will compile differently in each case, so it's a compile time error to use the push-receiving methods if on OS X or non-Android Java. But we could have a method/constant/something to determine it programatically at runtime, specially given we're adding push-receiving support for browsers (JS).
My proposal would be
rest.push.canActivate() -> Bool
. If it returns true, then therest.push.activate
method exists.Alternative names:
canReceive
,canRegister
. The former might be misleading since maybe it can't receive for case-specific reasons even if the platform is able to (e. g. the user didn't give permission); the latter is more precise but it lacks consistency with theactivate
method.┆Issue is synchronized with this Jira Task by Unito
The text was updated successfully, but these errors were encountered: