Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider wiring gulplog v1 handlers and print deprecation warning when used. #249

Closed
phated opened this issue Jan 7, 2024 · 0 comments · Fixed by #266
Closed

Consider wiring gulplog v1 handlers and print deprecation warning when used. #249

phated opened this issue Jan 7, 2024 · 0 comments · Fixed by #266
Assignees
@phated @sttk
Projects
v5

Comments

@phated
Copy link
Member

phated commented Jan 7, 2024

gulplog v2 doesn't see gulplog v1 messages (see gulpjs/gulplog#17). We should either implement a workaround here (or in gulplog itself) where the old messages are handled but print a deprecation warning.
@phated phated assigned phated and sttk Jan 7, 2024
@phated phated added this to To do in v5 via automation Jan 7, 2024
@phated phated mentioned this issue Feb 14, 2024
Closed
@sttk sttk mentioned this issue Feb 17, 2024
Closed
This was referenced Mar 23, 2024
Merged
Merged
@phated phated moved this from To do to In progress in v5 Mar 23, 2024
v5 automation moved this from In progress to Done Mar 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@phated phated

@sttk sttk

Labels
None yet
Projects
No open projects
v5
  
Done
Milestone
No milestone
2 participants
@phated @sttk