Skip to content

Conversation

@mcollina
Copy link
Member

Fixes FastifyWarning FSTWRN003 by removing async/callback mixing in listen calls.

Changed 26 instances across 6 test files.

Changed fastify.listen() calls to avoid mixing callback and promise styles that caused FastifyWarning FSTWRN003.

Co-Authored-By: Claude <noreply@anthropic.com>
@mcollina mcollina requested a review from gurgunday October 24, 2025 21:58
@Fdawgs Fdawgs requested a review from Copilot October 25, 2025 06:32
Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR fixes Fastify warning FSTWRN003 by removing the problematic mixing of async/await and callback patterns in fastify.listen() calls across test files.

Key Changes:

  • Removed async keyword from callback functions passed to fastify.listen() in 25 test cases
  • Converted one test to use proper async/await pattern without callbacks

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file
File Description
test/multipart.test.js Removed async keyword from 8 fastify.listen() callback functions
test/multipart-security.test.js Removed async keyword from 6 fastify.listen() callback functions
test/multipart-json.test.js Removed async keyword from 8 fastify.listen() callback functions
test/multipart-http2.test.js Converted test to properly use async/await with fastify.listen() instead of callback pattern
test/multipart-concat.test.js Removed async keyword from 2 fastify.listen() callback functions
test/multipart-body-schema.test.js Removed async keyword from 2 fastify.listen() callback functions

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copy link
Contributor

@Uzlopak Uzlopak left a comment

Choose a reason for hiding this comment

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

LGTM

Did this previously pollute the Testlogs with Warnings?

@mcollina
Copy link
Member Author

Yes

Copy link
Member

@gurgunday gurgunday left a comment

Choose a reason for hiding this comment

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

lgtm

Signed-off-by: Aras Abbasi <aras.abbasi@googlemail.com>
@mcollina mcollina merged commit 275c43d into main Oct 26, 2025
17 checks passed
@Uzlopak Uzlopak deleted the fix-warnings branch October 26, 2025 16:25
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