Version 6.1.0 of eslint-plugin-jsx-a11y was just published.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-jsx-a11y is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 5.0.10 of sinon was just published.

This version is covered by your current version range and after updating it in your project the build failed.

sinon is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

[0] is fomorian
[1] is razorback
[2] is unknown

Tried to test how it works (since there isn't much to read about) by running the code provided by the README

var WorldState = require('warframe-worldstate-parser');
var worldStates = {
  PC : new Worldstate('PC'),
  PS4 : new Worldstate('PS4'),
  X1 : new Worldstate('X1'),
}
var primeAccess = null;
worldStates[PC].getPrimeAccessString(function(err, primeAccessObject) {
  if (err) {
    return console.err(err);
  }
  primeAccess = primeAccessObject;
});

Sadly after running it I got the following error

ReferenceError: Worldstate is not defined
    at Object.<anonymous> (removedForObviousReasons\test.js:3:12)
    at Module._compile (module.js:410:26)
    at Object.Module._extensions..js (module.js:417:10)
    at Module.load (module.js:344:32)
    at Function.Module._load (module.js:301:12)
    at Function.Module.runMain (module.js:442:10)
    at startup (node.js:136:18)
    at node.js:966:3

I'm sorry if I misunderstood something of the code that is provided.

EDIT: Grammar and markup fix

ie:

• Fomorian
• Razorback

Test the parsers using actual data from worldstate to ensure that there are no major error or crashes

make the language on the conclave strings more natural

There does not appear to be a pattern to this. Other alerts with different mission types have showed as Ancient Retribution. It happens both with Genesis and my other bots that use this module.

Version 7.8.0 of eslint-plugin-react was just published.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Void Fissures use the same mission type that the mission was on, originally, and so if we map the solNodes to both name and mission type

add a wraith item type for tracking them

move day/night cycle calculation from genesis to worldstate and make it easier to fetch for others and not calculate every call

Version 3.2.0 of sinon-chai was just published.

This version is covered by your current version range and after updating it in your project the build failed.

sinon-chai is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Change getAlertsAsString to getAlertsString in the readme, or vice versa in the files. And make a not in the readme that it's not done yet and currenttly commented out. Also do this to a ton of other things.

and a simple example of how to import this project and include it might be nice.

Also the installation instruction should include the npm command to install from the github if that is the recomended version to use as expressed in the Readme.

need to add lunaro strings for conclave challenges

hey is this dead*?
can you show some example, thank you

Various objects in the parser automatically generate an identifier where the official API doesn't provide any. These objects however rely on the names of items after they've either been normalized or mapped using data from warframe-worldstate-data. This in turn means that if warframe-worldstate-data updates the mapping of a string - or if the normalization process changes - the identifier will "erroneously" change.

A FlashSale make for a great example:

{
  "item": "Tn S M G Weapon", 
  "expiry": "2018-12-31T00:00:00.000Z", 
  "discount": 0, 
  "premiumOverride": 240, 
  "isFeatured": true, 
  "isPopular": false, 
  "id": "1546214400000Tn S M G Weapon", 
  "expired": false, 
  "eta": "352d 18h 29m 35s"
}, 

In this case when /Lotus/Weapons/Tenno/LongGuns/TnSMG/TnSMGWeapon is identified in warframe-worldstate-data this deal's id would change, even though no deals have been added, removed or changed.

I propose that all generated ids are changed to only use "reliable" information. For the example above a possible updated id could be: 1546214400000TnSMGWeapon, using only the last segment of the original identifier string.

I'd be willing to help implement this if necessary.

Idea:

• Allow the consumer to specify a language (eg. english, spanish, etc) to look up a string for

Implementation arch:

• Default to what is currently returned if there is no language provided in whatever release the consumer is dependent on, but if data['${language}'] exists, use that instead.

write translation from internal strings for items to language strings

Version 2.13.0 of eslint-plugin-import was just published.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-import is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 7.9.0 of eslint-plugin-react was just published.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-react is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Version 15.5.1 of semantic-release was just published.

This version is covered by your current version range and after updating it in your project the build failed.

semantic-release is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The documentation should be improved by adding typedefs for all the worldstate data parameters and the dependencies object(s)