issue: make clients accept strings and typed objects for resource names

[anguillanneuf]

Currently the admin client expects strings

python-pubsublite/samples/snippets/get_lite_topic_example.py

Lines 40 to 42 in 9ca10e5

	topic_path = str(TopicPath(project_number, location, topic_id))
	response = client.get_topic(topic_path)

while the publisher and subscriber clients expect typed object.

python-pubsublite/samples/snippets/publisher_example.py

Lines 40 to 42 in 9ca10e5

	topic_path = TopicPath(project_number, location, topic_id)
	with make_publisher(topic_path) as publisher_client:

Ideally we shall accept both formats.

[dpcollins-google]

Ideally we shall accept both formats.

I don't agree with this, the wrapper objects cleanly isolate parsing vs client errors, and have a "parse" method to get this from the underlying string. I'm going to change the admin layer to just accept the wrappers for consistency, is this an acceptable end-state? It would mean you'd call:

response = client.get_topic(TopicPath(project_number, location, topic_id))
or
response = client.get_topic(TopicPath.parse("projects/xxx/locations/xxx/topics/xxx"))

[dpcollins-google]

I just checked this: The following code will not type check:

 topic_path = str(TopicPath(project_number, location, topic_id)) 
  
 response = client.get_topic(topic_path) 

If you ran it through pytype, it would fail. The current state is the proposed end state, it just happens to work when you pass it a string path.

[anguillanneuf]

Okay, you can just accept the wrappers for consistency.

[dpcollins-google]

Then this can be closed as they already only accept the wrappers.