Inconsistent ruleset/workspace name

[SrodriguezO]

The ruleset is name rules_play_routes but its workspace and is named io_bazel_rules_play_routes.

We should rename the workspace to rules_play_routes.

[borkaehw]

I noticed that before, but it seems to be the convention of Bazel ruleset. rules_go and rules_docker do the same.

[JaredNeil]

This page explains the standard naming conventions: https://docs.bazel.build/versions/master/skylark/deploying.html

[borkaehw]

If your rules belong to the bazelbuild organization, you must use rules_<lang> (e.g. rules_mockascript). Otherwise, you should name your repository <org>_rules_<lang> (e.g. build_stack_rules_proto).

Should it be lucidsoftware_rules_play_routes in our case?

[SrodriguezO]

Should it be lucidsoftware_rules_play_routes in our case?

I'm fine with going with that for the workspace name. It still wouldn't match the git repo name though.

Trying to get these into bazelbuild might be a good option (along with rules_twirl).

[borkaehw]

As far as I can see, most of the rules that live in bazelbuild have prefix io_bazel_, same as what we currently have.

[SrodriguezO]

Hmm I think you're right. It seems nobody's following the standard convention 🙃

[JaredNeil]

Well it was just standardized 16 days ago in bazelbuild/bazel#8884