fix: polish the force permission level example #2103
Merged
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
github-actions
bot
added
the
t-core-services
|
Preview for this PR was built for commit |
raethlo
added
the
validated
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I randomly noticed this.
**were presumably supposed to make the param bold but it did not work 😄Note
Polishes the limited-permissions examples by adding the missing constant import and fixing the API query parameter formatting.
import { ACTOR_PERMISSION_LEVEL } from '@apify/consts'forforcePermissionLevelusage.POST /v2/acts/<actor_id>/runs?forcePermissionLevel=LIMITED_PERMISSIONSformatting by removing incorrect bold markup.Written by Cursor Bugbot for commit 05ac2dc. Configure here.