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
This was already an idea that twilight siggested, but I wanted to make this suggestion to maybe give a idea of how it could work.
It would be a breaking change, but my idea is that validate would be able to return 4 values, "search", "track", "playlist" or null. If not null, validate is successful. For queryResolver, it would call all extractor's validate method, and for the one that doesnt return null, it would know what extractor can handle the query, and the type of said query, so QueryResolver could return the identifier of the successful extractor, and the type (example: { ext: "com.discord-player.soundcloud", type: "search" }), so it could be better used in code to know what a query is supposed to be before playing it.
Expected behavior
Screenshots
Additional context
The text was updated successfully, but these errors were encountered:
Describe the feature you would like
This was already an idea that twilight siggested, but I wanted to make this suggestion to maybe give a idea of how it could work.
It would be a breaking change, but my idea is that validate would be able to return 4 values, "search", "track", "playlist" or null. If not null, validate is successful. For queryResolver, it would call all extractor's validate method, and for the one that doesnt return null, it would know what extractor can handle the query, and the type of said query, so QueryResolver could return the identifier of the successful extractor, and the type (example: { ext: "com.discord-player.soundcloud", type: "search" }), so it could be better used in code to know what a query is supposed to be before playing it.
Expected behavior
Screenshots
Additional context
The text was updated successfully, but these errors were encountered: