Develop -> Feature | Added documentation for custom data support in debug panel #212
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
Added: initial documentation Added: reference image Added: description and example Added: example color codes Updated: improved readability
…-custom-data' into feature/vaah-flutter-debug-panel-custom-data
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
we-mohd-i001
added
documentation
feature -> develop | Code walkthrough and environment updated
…-custom-data' into feature/vaah-flutter-debug-panel-custom-data
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.
Task #9857 - VaahDocs > VaahFlutter > Debug Panel > Add Custom Data Support
Time invested: hh:mm format | Billable: 08:40 | Non-Billable: 00:00
Proof of your testing, video, or image link?
Demo Url:-
Problem Statement-
Describe The fix/ Solution
Self review checklist
featurewithdevelop?comments¬esinwireframeand verified that you have taken care of that?UImust match withdesign&wireframeif available?developexists in yourfeaturebranch after rebase?featureas per the client requirement?