This maintains the wrong stack. The stack that needs to be maintained is a level higher than the plugin instances. The tests all pass because they only run against a set with a single element.
Maintaining a higher stack is barely feasible. And not that useful anyway: The widget method is a getter, which always work with only the first element. So having .end() return that element makes perfect sense.
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.
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products.
Learn more.
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products.
You can always update your selection by clicking Cookie Preferences at the bottom of the page.
For more information, see our Privacy Statement.
Essential cookies
We use essential cookies to perform essential website functions, e.g. they're used to log you in.
Learn more
Always active
Analytics cookies
We use analytics cookies to understand how you use our websites so we can make them better, e.g. they're used to gather information about the pages you visit and how many clicks you need to accomplish a task.
Learn more
This comment has been minimized.
This maintains the wrong stack. The stack that needs to be maintained is a level higher than the plugin instances. The tests all pass because they only run against a set with a single element.
This comment has been minimized.
Maintaining a higher stack is barely feasible. And not that useful anyway: The widget method is a getter, which always work with only the first element. So having .end() return that element makes perfect sense.