Skip to content

Conversation

@halx99
Copy link
Collaborator

@halx99 halx99 commented Jul 23, 2025

Describe your changes

Issue ticket number and link

Checklist before requesting a review

For each PR

  • Add Copyright if it missed:
    - "Copyright (c) 2019-present Axmol Engine contributors (see AUTHORS.md)."

  • I have performed a self-review of my code.

    Optional:

    • I have checked readme and add important infos to this PR.
    • I have added/adapted some tests too.

For core/new feature PR

  • I have checked readme and add important infos to this PR.
  • I have added thorough tests.

Axmol 3.x ------------------------------------------------------------

For each 3.x PR

  • Check the '#include "axmol.h"' and replace it with the needed headers.

@halx99 halx99 added this to the 3.0.0 milestone Jul 23, 2025
@halx99 halx99 added the enhancement New feature or request label Jul 23, 2025
@halx99 halx99 linked an issue Jul 23, 2025 that may be closed by this pull request
@halx99 halx99 added bug Something isn't working and removed enhancement New feature or request labels Jul 23, 2025
@halx99 halx99 force-pushed the fix-incorrect-format-to-use branch from d191d4c to c009e71 Compare July 23, 2025 09:21
@halx99 halx99 force-pushed the fix-incorrect-format-to-use branch from c009e71 to 2099934 Compare July 23, 2025 10:24
@halx99 halx99 merged commit af16799 into wip-v3 Jul 23, 2025
15 of 16 checks passed
@halx99 halx99 deleted the fix-incorrect-format-to-use branch July 23, 2025 10:24
@halx99 halx99 modified the milestones: 3.0.0, 2.8.0 Jul 23, 2025
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

None yet

Development

Successfully merging this pull request may close these issues.

Incorrect fmt::format_to use for c style string

2 participants