doc: clarify using fleet api has lots of drawbacks #4173
Merged
Conversation
This file contains 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
1 task
✅ Deploy Preview for teslamate ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
1 task
JakobLichterfeld
changed the title
|
@JakobLichterfeld Yeah, this is much clearer, thanks! |
|
Great job 👏 |
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.
Thank you. Since you were the first to stumble, you won't be the last. So I am always open to improvements and I understand your point.
This was the point that stopped me from merging or implementing the Fleet API in the first place, as there are only drawbacks for 99.9% of users.
Using the fleet API is not recommended and has not been recommended in any issue or discussion.
The name official indicates something else, I got this point.
Originally posted by @JakobLichterfeld in #4081 (comment)