Closed neo-angeiras closed 3 months ago
So the reason why it's probably complain is because when you add //
comments outside of PHP, it treats that like regular ol' plain text. The reason why it works in 2.0.2 is because it used to wipe out any output buffer before it even got started. You actually could probably have it still work <3.5.0 if you wanted. You also could use Flight::set('flight.v2.output_buffering', true);
to make it work like it used to.
My recommendation going forward would be to put your comments actually inside the <?php
tags so they are treated as such. Having "comments" outside of PHP code is not an intended use case.
To further add: it's not that comments written before <?php
are treated like regular text it's that PHP doesn't even parse anything outside of a PHP tag it's and is simply kept as-is and added to the content of the page.
This is by design and a great example of why is actually on the PHP wiki:
<!DOCTYPE html>
<html>
<head>
<title>PHP Test</title>
</head>
<body>
<?php echo '<p>Hello World</p>'; ?>
</body>
</html>
I already adjust all my PHP files, just a few for my first Flight API (and, in fact, my first ever PHP job)
Thanks for the response.
Congrats on your first job! I remember my first job and how exciting it was. Please keep in touch to see how we can help you be as successful as possible!
When I add a comment before php begin tag (<?php), the json returned by Flight::json(...) includes the comment. For instance:
should return only :
but returns:
If the comment goes after <?php, it returns without garbage In flight 2.0.2, with same php version (7.4), works fine