Change naming of the id field of namespace resource to make it more self-explanatory

[kavalerov]

Currently the field is called ID, based on the naming adopted in the Control API.

This name is not very self-explanatory, as according to the documentation it is

"The namespace or channel name that the channel rule will apply to. For example, if you specify namespace the namespace will be set to namespace and will match with channels namespace:* and namespace."

On the Namespaces endpoint, when we want to create a new namespace the field that contains the channel name or namespace filter is called id: https://ably.com/docs/api/control-api#tag/namespaces/paths/~1apps~1{app_id}~1namespaces/post. Similarly it is called id when we just get a list of namespaces.

This seems to be a very confusing name for what it is. This also additionally adds to the confusion that the same functionality in the dashboard is called “Channel Rules”, and corresponding field is called “Namespace or Channel ID” in the UI.

┆Issue is synchronized with this Jira Task by Unito

[kavalerov]

Related internal discussion: https://ably-real-time.slack.com/archives/C01B5JK1TB4/p1660918455458259

[sync-by-unito]

➤ Automation for Jira commented:

The link to the corresponding Jira issue is https://ably.atlassian.net/browse/SDK-3043