This repository has been archived by the owner on Dec 19, 2018. It is now read-only.
CodeGeneration should not generate line pragmas from unknown file paths #1110
Comments
NTaylorMullen
added a commit
that referenced
this issue
Apr 4, 2017
- Prior to this change default imports would get line pragmas generated for them because thye'd have a source location but no file path (they were a dynamic document). - Re-generated C# files to reflect new line pragma changes. #1110
NTaylorMullen
added a commit
that referenced
this issue
Apr 4, 2017
- Prior to this change default imports would get line pragmas generated for them because thye'd have a source location but no file path (they were a dynamic document). - Re-generated C# files to reflect new line pragma changes. #1110
NTaylorMullen
added a commit
that referenced
this issue
Apr 4, 2017
- Prior to this change default imports would get line pragmas generated for them because thye'd have a source location but no file path (they were a dynamic document). - Re-generated C# files to reflect new line pragma changes. #1110
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In the case of MVC extensions we generate dynamic
_ViewImports.cshtmlfile equivalents that don't end up having any actual existence on disk. When one of those files has an@using Foowe codegen a line pragma forFoothat does not have a filename. We don't want innaccurate line pragma errors due to lack of file name so we shouldn't render a pragma if a filename is not set on a source location.The text was updated successfully, but these errors were encountered: