Fixed
Status Update
Comments
an...@google.com <an...@google.com>
ad...@gmail.com <ad...@gmail.com> #2
Should we transform it from
fun <FileTypeT: FileSystemLocation> add(
type: MultipleArtifact<FileTypeT>,
artifact: FileTypeT
)
to
fun <FileTypeT: FileSystemLocation, Appendable> add(
type: MultipleArtifact<FileTypeT>,
artifactProvider: Provider<FileTypeT>
)
should we also share with Artifacts interface: ArtifactsImpl.appendTo ArtifactsImpl.appendAll. They are not in use right now. Maybe part of another ticket?
di...@google.com <di...@google.com> #3
I don't think we can just move it to use a Provider<> as the original bug called for adding a file.
plus this add() would become just like to OperationRequest::toAppendTo no ?
Description
# It is OK to share your API Project ID, but _not_ API keys.
Feature Request
-----------------------
What would you like to see us add to this API?
I'm filing this feature request to have the ability to set strict bounds when making iOS Places autocomplete requests.