Skip to content

Skip writing functions.metadata when using source gen #2974

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

Open
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

jviau
Copy link
Contributor

@jviau jviau commented Mar 3, 2025

Issue describing the changes in this PR

resolves #1058

Pull request checklist

  • My changes do not require documentation changes
    • Otherwise: Documentation issue linked to PR
  • My changes should not be added to the release notes for the next release
    • Otherwise: I've added my notes to release_notes.md
  • My changes do not need to be backported to a previous version
    • Otherwise: Backport tracked by issue/PR #issue_or_pr
  • I have added all required tests (Unit tests, E2E tests)

Additional information

Skips writing functions.metadata when using source gen version of function metadata provider.

<FunctionsAutoRegisterGeneratedMetadataProvider>$(FunctionsEnableWorkerIndexing)</FunctionsAutoRegisterGeneratedMetadataProvider>
<FunctionsAutoRegisterGeneratedMetadataProvider>$(FunctionsEnableWorkerIndexing)</FunctionsAutoRegisterGeneratedMetadataProvider>
<_WriteFunctionsMetadata>true</_WriteFunctionsMetadata>
<_WriteFunctionsMetadata Condition="'$(FunctionsEnableMetadataSourceGen)' == 'true'">false</_WriteFunctionsMetadata>
Copy link
Member

Choose a reason for hiding this comment

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

Do we also want to give users the ability to override this behavior? I don't have a concrete scenario in mind, but if users have a dependency on that file for anything, having a property they can set would help preserve this behavior until the next major version, where we can permanently remove it.

Copy link
Contributor Author

@jviau jviau Mar 5, 2025

Choose a reason for hiding this comment

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

What should our default be? Write or don't write? I have it as default don't write for now, which could be considered a breaking change?

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.

Skip creating functions.metadata when source gen version of function metadata provider is enabled
2 participants