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
Currently we have the ScopeManager interface and various packages/classes that use the scope name. The recent introduction of the Context into the specification as well as the Context API PR #792 make me think we might be better off renaming scope to context now before we reach beta stability.
The text was updated successfully, but these errors were encountered:
Digged to find why we used Scope instead of Context, coming from there: #66 (comment). Since we will have a single concept from now on i believe it's fine to rename them.
Currently we have the
ScopeManager
interface and various packages/classes that use the scope name. The recent introduction of theContext
into the specification as well as the Context API PR #792 make me think we might be better off renaming scope to context now before we reach beta stability.The text was updated successfully, but these errors were encountered: