Skip to content

Add bower file so we can register with bower registry. #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 17, 2016

Conversation

mikeproeng37
Copy link
Contributor

@optimizely/fullstack-devs

@mikeproeng37 mikeproeng37 merged commit 7c73e63 into devel Nov 17, 2016
@mikeproeng37 mikeproeng37 deleted the mng/add-to-bower branch November 17, 2016 18:39
mjc1283 added a commit that referenced this pull request Apr 22, 2019
…of project config and into decision service (#24)

Summary:

This is a solution for persisting forced variation state when the project config is updated from datafile management. Just as in Java, we moved the forced variation map and forced variation methods into decision service.

Test plan:

- Existing unit tests are passing with no substantial changes: the changes I made in existing unit tests only update log message assertions to reflect the new location of forced variation methods (previously in project config, now in decision service).

- I moved forced variation method tests to the decision service tests file, and updated the method signatures to remove the logger argument (decision service already has a reference to its own logger).

- I added a few more unit tests covering cases where a previously set variation or experiment no longer exists on a new project config object.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants