Handle queries (i.e. "?name=Pikachu")

[seriema]

Currently query parameters in the API URL are just stripped out. There should be an optional setting for including them in the redirect.

Use case Better testing of search-like features where one could test search terms that will give different search results, such as no results, a few results, a lot of results, spelling suggestions, etc.

Usage Config set in the config() by setting stripQueries to false (default is true). Sample:

angular.module('testApp', ['apiMock'])
.config(function (apiMockProvider) {
  apiMockProvider.config({
    stripQueries: false
  });
});

Descoped (do this later as a separate feature): Local and global flag set on individual requests, which would be perfect for isolated testing of a autocompletion type search. To not pollute the $http config we should scope it within apiMock, but that requires another feature (to allow config objects instead of just true/false). Sample:

app.service('exampleService', function ($http) {
  // ...
  $http({
    method: 'GET',
    url: '...',
    apiMock: {
      stripQueries: true
    }
  }) // ...
  // ...
});

Effect

• Changes redirect logic so that /api/pokemon?name=Pikachu no longer strips the query and redirects to /mock_data/pokemon.get.json. Instead it redirects to /mock_data/pokemon/name=pikachu.get.json (similar to #13 where /api/pokemon would redirect to /mock_data/pokemon/get.json instead of /mock_data/pokemon.get.json, but for now we only do this for URL's with queries).
• It will lowercase and URI encode the queries (i.e. Pikaču becomes pika%C4%8Du).
• It will sort the query params in alphabetical ascending order (i.e. strength=...&name=... becomes name=...&strength=...).

[trevcor]

Still trying to steal some time away to work on this. Hopefully be done this week.

[seriema]

No problem! I'd love to hear your comments on the questions above.

[trevcor]

Had some time to look around more of the code and think about your questions.

1. I agree we should lowercase the query values by default but give a config to override that behavior. I think the query param name should stay as it is. Should we call the config forceLowerCaseQueries and default to true?
2. Yep I like this pattern way better than the underscore.
3. Agreed. Default to true makes more sense.
4. Yeah this makes sense.
5. I'm still looking at that commit. When I view it in github it looks like the entire file was changed so its tough to see what exactly the change was.
6. I also agree with this. Let's get the global stuff working and then we can add the targeted api feature later.

So for the global feature we will add 2 config options, forceLowerCaseQueries, stripQueries.

Anything else?

[seriema]

1. If the request comes up we can add the flag. I can't find a good use case for mixed casings and it would just add more code/tests unnecessarily. For now let's just have lowercase as default.
2. Yeah it's annoying (hence why I request clean diffs in the contribution guidelines now), but ctrl+f for "appendParamsToPath" and you should see it.

Thanks!

[seriema]

If anyone wants to discuss this feature, I've opened a Gitter chatroom.