This repository was archived by the owner on Sep 21, 2022. It is now read-only.
feat: Add ability to pass any event arguments amount via PassthroughEmitter#917
Open
feat: Add ability to pass any event arguments amount via PassthroughEmitter#917
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Текущий PassthroughEmitter имеет 1 "фатальный недостаток": можно использовать только 1 параметр для события.
Данный пулл-реквест устраняет это ограничение.
P.S. текущие юнит тесты на
PassthroughEmitterнаписаны неправильно, так как используетсяassert.equalвместоassert.deepEqual.Например существующий тест:
Здесь data, которая возвращается из промиса - это фактически двойной вложенный массив, который образуется путем двухкратного применения
waitForResultsизemitAndWaitклассаAsyncEmitterв gemini-core. Т.е. реальное значениеdata- это[['some-data']].Корректно данная проверка выглядела бы следующим образом:
То, что сейчас этот тест проходит - это особенность работы assert.equal