FsLexYacc.targets does not register .fsl and .fsy files as build inputs for the IDE's fast up-to-date check, so an IDE can consider a project up to date after a grammar has been edited and skip the build.
dotnet/fsharp's copy of these targets (buildtools/buildtools.targets) does register them:
<!-- Register .fsl/.fsy files as build inputs for IDE fast up-to-date checks -->
<ItemGroup>
<UpToDateCheckInput Include="@(FsLex)" />
<UpToDateCheckInput Include="@(FsYacc)" />
</ItemGroup>
The package's version has no equivalent. This looks like another fix that was made downstream in dotnet/fsharp and never came back here, alongside the two CallFsYacc bugs discussed in #231.
Adding the same item group to src/FsLexYacc.Build.Tasks/FsLexYacc.targets should be all that is needed.
FsLexYacc.targetsdoes not register.fsland.fsyfiles as build inputs for the IDE's fast up-to-date check, so an IDE can consider a project up to date after a grammar has been edited and skip the build.dotnet/fsharp's copy of these targets (
buildtools/buildtools.targets) does register them:The package's version has no equivalent. This looks like another fix that was made downstream in dotnet/fsharp and never came back here, alongside the two
CallFsYaccbugs discussed in #231.Adding the same item group to
src/FsLexYacc.Build.Tasks/FsLexYacc.targetsshould be all that is needed.