You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
eject is currently treated as a command rather than an operation on commands, and as such any given command's eject method is passed a unique Helper rather than that associated with the command. As a result, it is not possible to access the command's options in the dojorc, as the helper's configuration uses eject as its internal key, so helper.configuration.get() actually reads from the non-existent eject key. This also means that calling helper.configuration.set() from within eject methods across commands results in multiple writes to the same object.
Bug
eject
is currently treated as a command rather than an operation on commands, and as such any given command'seject
method is passed a uniqueHelper
rather than that associated with the command. As a result, it is not possible to access the command's options in the dojorc, as the helper's configuration useseject
as its internal key, sohelper.configuration.get()
actually reads from the non-existenteject
key. This also means that callinghelper.configuration.set()
from withineject
methods across commands results in multiple writes to the same object.Package Version:
Code
Expected behavior:
{ "hello": "world" }
is logged to the console and thedojorc
is updated to:Actual behavior:
{}
is logged to the console as there is noeject
key, and the dojorc is updated to:The text was updated successfully, but these errors were encountered: