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.

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

Rename FSharpReferencedProject.ProjectFileName for clarity #12431

Merged
merged 1 commit into from
Nov 23, 2021

Conversation

baronfel
Copy link
Member

This renames the projectFileName field and FileName property to reflect the
actual use: the project's output file. This was unclear based on docs, but clear based on usage,
and so docs were added to help ensure correct usage.

@baronfel
Copy link
Member Author

Tagging @Krzysztof-Cieslak for review (since he found this mismatch in the first place).

@Krzysztof-Cieslak
Copy link
Contributor

👍 for the change, the naming caused regression in Ionide (proj-info) because when updating to the latest FCS we thought it's about path to .fsproj rather than path to .dll

This renames the `projectFileName` field and `FileName` property to reflect the
actual use: the project's output file. This was unclear based on docs, but clear based on usage,
and so docs were added to help ensure correct usage.
@baronfel baronfel force-pushed the fsharpreferencedproject-docs branch from 2d2af04 to 97c51d0 Compare November 19, 2021 21:17
@vzarytovskii vzarytovskii merged commit 69ece79 into dotnet:main Nov 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants