8000 ci(travis): add mdspell by juancarlostong · Pull Request #316 · optimizely/android-sdk · GitHub
[go: up one dir, main page]
Skip to content
8000

ci(travis): add mdspell #316

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.

Sign up for GitHub

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 3 commits into from
Feb 10, 2020
Merged

ci(travis): add mdspell #316

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
86b6e9c
ci(travis): add mdspell
juancarlostong Feb 7, 2020
e960d54
use latest version of .spelling
juancarlostong Feb 7, 2020
f47f0a1
spelling fixes
juancarlostong Feb 7, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions .travis.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -69,6 +69,19 @@ jobs:
notifications:
email: false

- stage: 'Lint markdown files'
language: node_js
node_js: 12
os: linux
before_install: skip
install:
- npm i -g markdown-spellcheck
before_script:
- wget --quiet https://gist.githubusercontent.com/juancarlostong/dad02feeebc8763af35b4fdc717cf7a2/raw/.spelling
script:
- mdspell -a -n -r --en-us '**/*.md'
after_success: skip

- &integrationtest
stage: 'Integration tests'
addons:
Expand Down
16 changes: 8 additions & 8 deletions CHANGELOG.md
View file
Open in desktop
8000
Original file line number Diff line number Diff line change
Expand Up @@ -218,7 +218,7 @@ The primary difference between the new Feature Variable APIs and the older, Vari
To learn more about Feature Management, read our [knowledge base article introducing the feature](https://help.optimizely.com/Set_Up_Optimizely/Develop_a_product_or_feature_with_Feature_Management).

### New Features
* Introduces the `isFeatureEnabled` API, a featue flag used to determine whether to show a feature to a user. The `isFeatureEnabled` should be used in place of the `activate` API to activate experiments running on features. Specifically, calling this API causes the SDK to evaluate all [Feature Tests](https://developers.optimizely.com/x/solutions/sdks/reference/?language=android#activate-feature-tests) and [Rollouts](https://developers.optimizely.com/x/solutions/sdks/reference/?language=android#activate-feature-rollouts) associated with the provided feature key.
* Introduces the `isFeatureEnabled` API, a feature flag used to determine whether to show a feature to a user. The `isFeatureEnabled` should be used in place of the `activate` API to activate experiments running on features. Specifically, calling this API causes the SDK to evaluate all [Feature Tests](https://developers.optimizely.com/x/solutions/sdks/reference/?language=android#activate-feature-tests) and [Rollouts](https://developers.optimizely.com/x/solutions/sdks/reference/?language=android#activate-feature-rollouts) associated with the provided feature key.
```
Boolean enabled = optimizelyClient.isFeatureEnabled("my_feature_key", "user_1", userAttributes);
```
Expand Down Expand Up @@ -252,7 +252,7 @@ optimizelyManager.initialize(this, new OptimizelyStartListener() {
### Deprecations
* Version 2.1.0 deprecates the Variable APIs: `getVariableBoolean`, `getVariableFloat`, `getVariableInteger`, and `getVariableString`

* Replace use of the Variable APIs with Feature Mangement's Feature Variable APIs, described above
* Replace use of the Variable APIs with Feature Management's Feature Variable APIs, described above

* We will continue to support the Variable APIs until the 3.x release, but we encourage you to upgrade as soon as possible

Expand Down Expand Up @@ -421,7 +421,7 @@ optimizelyClient.track("event_key", "user_id", userAttributes, eventTags);
- `getVariableFloat` now becomes `getFeatureVariableDouble`

## 1.6.0
Febuary 3, 2018
February 3, 2018

- Release 1.6.0

Expand Down Expand Up @@ -456,7 +456,7 @@ November 1, 2017
- Call start listener if there is an exception.
- Example of overriding Gson and android-logger in test-app gradle file.
- Fix crash on API 17 (missing annotation).
- Support for Android O (please see developer docs for details). Basically, Android O and above will use JobScheduler and pre Android O will continue to use AlarmService. This is done through a class called the JobWorkService which allows you to keep your Service and IntentService intact. Developers can piggyback on this method and keep thier IntentServices and use the JobWorkService.
- Support for Android O (please see developer docs for details). Basically, Android O and above will use JobScheduler and pre Android O will continue to use AlarmService. This is done through a class called the JobWorkService which allows you to keep your Service and IntentService intact. Developers can piggyback on this method and keep their IntentServices and use the JobWorkService.
- Proguard rules were broken and were causing event payload to be stripped to single character keys.

*Breaking Changes*
Expand Down Expand Up @@ -485,7 +485,7 @@ October 30, 2017
- Call start listener if there is an exception.
- Example of overriding Gson and android-logger in test-app gradle file.
- Fix crash on API 17 (missing annotation).
- Support for Android O (please see developer docs for details). Basically, Android O and above will use JobScheduler and pre Android O will continue to use AlarmService. This is done through a class called the JobWorkService which allows you to keep your Service and IntentService intact. Developers can piggyback on this method and keep thier IntentServices and use the JobWorkService.
- Support for Android O (please see developer docs for details). Basically, Android O and above will use JobScheduler and pre Android O will continue to use AlarmService. This is done through a class called the JobWorkService which allows you to keep your Service and IntentService intact. Developers can piggyback on this method and keep their IntentServices and use the JobWorkService.

*Breaking Changes*

Expand Down Expand Up @@ -703,10 +703,10 @@ October 27, 2016
- If a service is scheduled when rescheduling the old service will be unscheduled.
- Now multiple `OptimizelyManager`instances can be created for multiple Optimizely X projects.
- A manager builds `AndroidOptimizely` for the project id it was created with and only that that project id.
- Could run one project in your activites and one in your services.
- Could run one project in your activities and one in your services.
- Now shows user experiment record logs.
- Turns on more core logs.

*New Features*
- *Exponential Backoff.* Datafile download event dispatching now exmploy exponential backoff.
- *Preemptive Wifi Event Flushing.* If event flushing is scheduled and wifi becomes available Optmizely will preemptively attempt to flush events before the next interval occurs. If flushing occurs the flushing will be rescheduled.
- *Exponential Backoff.* Datafile download event dispatching now employs exponential backoff.
- *Preemptive Wifi Event Flushing.* If event flushing is scheduled and wifi becomes available Optimizely will preemptively attempt to flush events before the next interval occurs. If flushing occurs the flushing will be rescheduled.
0