Fix flowtrackd naming in schema map #22978
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hyperlint-ai
bot
requested review from
a team,
angelampcosta and
soheiokamoto
as code owners
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
![windsurf-bot[bot]](https://avatars.githubusercontent.com/in/1066231?s=60&v=4){kind=small}
| In this example, we are going to use the GraphQL Analytics API to query for Firewall Events over a specified time period. | ||
|
|
||
| The following API call will request Firewall Events over a one hour period, and output the requested fields. Be sure to replace `<CLOUDFLARE_ZONE_TAG>`, `<EMAIL>`, and `<API_TOKEN>`[^1] with your zone tag and API credentials, and adjust the `datetime_geg` and `datetime_leq` values to your liking. | ||
| The following API call will request Firewall Events over a one hour period, and output the requested fields. Be sure to replace `<Cloudflare_ZONE_TAG>`, `<EMAIL>`, and `<API_TOKEN>`[^1] with your zone tag and API credentials, and adjust the `datetime_geq` and `datetime_leq` values to your liking. |
Contributor
There was a problem hiding this comment.
There's a typo in the parameter name in the text. It says 'datetime_geg' in the original text which was corrected to 'datetime_geq' in this PR, matching the actual parameter used in the code example.
Comment on lines
+22
to
23
| <th>flowtrackedNetworkAnalytics-AdaptiveGroups</th> | ||
| <th>magicFirewallNetworkAnalytics-AdaptiveGroups</th> |
Contributor
There was a problem hiding this comment.
There's an inconsistency in the formatting between the two instances of 'flowtrackedNetworkAnalytics-AdaptiveGroups'. In the first instance (line 22), it's plain text in a tag, but in the second instance (line 323), it's wrapped in tags. For consistency, both instances should use the same formatting.
Contributor
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request addresses several spelling errors and formatting issues in the documentation, ensuring compliance with the style guide rules. Key changes include correcting misspellings, updating non-standard quotes, and fixing casing issues for specific terms.
schema-map.mdx)schema-map.mdx)schema-map.mdx)schema-map.mdx)schema-map.mdx)