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

Parse .NET .vbproj and .fsproj files as XML #4518

Merged
merged 3 commits into from
Sep 24, 2024
Merged

Conversation

bryceatmoderne
Copy link
Contributor

@bryceatmoderne bryceatmoderne commented Sep 23, 2024

What's changed?

.vbproj and .fsproj are .NET project XML files and need to be parsed as such.

What's your motivation?

Prior to these changes these file types were being parsed as PlainText.

Anything in particular you'd like reviewers to focus on?

No.

Anyone you would like to review specifically?

@timtebeek

Have you considered any alternatives or workarounds?

No.

Any additional context

No.

Checklist

  • I've added unit tests to cover both positive and negative cases
  • I've read and applied the recipe conventions and best practices
  • I've used the IntelliJ IDEA auto-formatter on affected files

@bryceatmoderne bryceatmoderne self-assigned this Sep 23, 2024
@bryceatmoderne bryceatmoderne added the bug Something isn't working label Sep 23, 2024
@bryceatmoderne bryceatmoderne changed the title Parse .vbproj and .fsproj as XML files Parse .NET .vbproj and .fsproj files as XML Sep 23, 2024
// .NET project files
"csproj",
"vbproj",
"fsproj"));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we also should add "targets" and "props" from the .NET ecosystem here or not. Thoughts?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think those were intentionally kept as plaintext, given any ambiguity in those file extensions being used elsewhere:
https://github.com/moderneinc/moderne-cli/pull/2117/files

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see. So allowing these mappings to be more dynamic (e.g. parse .props files as XML in .NET projects) seems like it will at some point become necessary.

@timtebeek
Copy link
Contributor

Already merging this now such that it makes it into today's release. Thanks both for your input!

@timtebeek timtebeek merged commit d2c825c into main Sep 24, 2024
2 checks passed
@timtebeek timtebeek deleted the parse-vbproj-as-xml branch September 24, 2024 12:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants