Support multiple controllers path

[salmanasiddiqui]

What? Why?

I ran into a problem in a Rails app which was made up of multiple Rails engines. The problem was that two engines were using Gruf and when they were used in same Rails app, the Gruf config for controllers_path was getting overridden.

So to fix that problem, I patched Gruf to support multiple paths for controllers by adding a new config field controllers_paths. This field defaults to [controllers_path]. Gruf uses this controllers_paths instead of controllers_path everywhere, but controllers_path is kept in config for backward compatibility.

Note: I think the config should support something like add_controllers_paths, instead of directly setting controllers_paths. That will allow multiple modules to add their controllers path without messing with the existing paths. Let me know if you like this idea, I will update the PR

How was it tested?

All the specs are passing

[salmanasiddiqui]

Hey @splittingred 👋🏽 , this PR is ready for review with the suggestion you made #213 (comment)

[salmanasiddiqui]

Hey @splittingred 👋🏽

this is the change you requested in #213 (comment)

I have updated this accordingly. Let me know if you would like any other change

[splittingred]

This is a breaking change; can we avoid this by just checking to see if the passed variable is an Enumerable, or a String, and handle it accordingly? That would satisfy the requirement without breaking the public contract.

[salmanasiddiqui]

i can leave the path keyword arg and additionally support paths. If both are passed then it would raise, otherwise path will be just wrapped in an array and set @paths

      def initialize(path: nil, paths: [], reloading: nil, tag: nil)
        raise ArgumentError(..) unless (path.nil? ^ paths.empty?)

        @paths = paths.empty? ? [path] : paths

[splittingred]

That's fine - we just need to make sure there's a backward-compatible deprecation path.