fix(api-schema): add missing 'effectivePlatformFeatures', 'createdAt', 'isPaying' to UserPrivateInfo #1569
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
…, 'isPaying' to UserPrivateInfo
fnesveda
approved these changes
May 12, 2025
metalwarrior665
added a commit
to apify/apify-client-js
that referenced
this pull request
May 13, 2025
… to User interface (#691) Prerequisite apify/apify-docs#1569 was merged Questions: 1. The string -> Date conversion happens automatically for all types, right? So no need to do anything? 2. Do we use explicit `T | null` anywhere if the API returns the type or null? Seems we like to do `T?` rather
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.
https://api.apify.com/v2/users/me?token=