Skip to content
This repository was archived by the owner on Oct 24, 2025. It is now read-only.

Conversation

@saper
Copy link
Member

@sapersaper commented Apr 18, 2016

Well, actually it seems fine. @am11 would be cool if you could have a look at this!

@coveralls
Copy link

Coverage Status

Coverage remained the same at 78.844% when pulling 8323d7b on saper:msb8012 into dad3022 on sass:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.6%) to 78.288% when pulling 8323d7b on saper:msb8012 into dad3022 on sass:master.

@am11
Copy link
Contributor

am11 commented Apr 19, 2016

Does renaming TargetPath to SasscPath fix the warning? (i.e. without defining extra variables)

@saper
Copy link
MemberAuthor

It might, actually my first thought was that this is just a coincidence...

@xzyfer
Copy link
Contributor

@saper any action to be taken here? Please ship it or close it :)

@xzyfer
Copy link
Contributor

VS build files have seen a lot of changes recently. Is this still relevant?

Sign up for freeto subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants

@saper@coveralls@am11@xzyfer@glebm