Conversation
|
Apologies I've just realised theres another PR open that addresses this, although I believe my solution is more flexible so I'll keep it open and it's up to you. |
|
please, i need this change... |
|
@benadamstyles @mcavaliere @BaseCase could you take a look when you get a chance please? |
benadamstyles
left a comment
benadamstyles
left a comment
There was a problem hiding this comment.
Code seems ok to me, I haven't had the chance to run it though
|
can you merge @mcavaliere @BaseCase ? thanks |
|
@benadamstyles can we merge this please? |
|
@benadamstyles @mcavaliere @BaseCase one last try |
|
Sorry I don't have write access, I can review but I can't merge! |
|
@BaseCase could you please merge the request? |
|
I forked this and published it to npm, since it's affecting our devs workflows at work. Please let me know if the PR is merged so that I can remove my fork. |
|
+1 on merging this. Pretty please with sugar on top? |
|
is it merged ? |
|
Still waiting for this PR to be merge |
|
I did the workaround. But if the pr is merged it will save some hassle
…On Tue, 6 Jul, 2021, 1:09 pm Agare Efe Knowledge, ***@***.***> wrote:
Still waiting for this PR to be merge
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AT66CY55CWV7F2D4V73OD3LTWKXKJANCNFSM4N3PSJBQ>
.
|
9 participants
No description provided.