This repository has been archived by the owner on Dec 12, 2024. It is now read-only.
Fix Parameter Naming in Cells Documentation (#49) #50
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
|
can someone check this |
|
@TanmayDhobale hey, not anymore, since you deleted the head repo. Besides, the original issue #49 was fixed earlier via a different PR. Thank you for your time though, there are many other issues you may help with in the future! But please wait a bit before #79 gets resolved, as it would involve many files and folders moving around :) |
|
Ahh got it |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Overview
This pull request aims to address the inconsistencies in parameter naming within the
cellssection of the Tact language documentation, as outlined in issue #49.Changes Made
Builder.storeBoolfunction description to improve clarity.cellssection, focusing on parameter naming and descriptions.Why This Change Is Necessary
The inconsistency in parameter naming within the documentation could potentially lead to confusion for developers trying to learn or implement the Tact language. By standardizing the naming convention and clarifying function descriptions, we aim to enhance the overall developer experience and facilitate easier learning and usage of the Tact language.
Impact
cellsdocumentation will now find a more consistent and clear set of instructions, potentially reducing learning curve and implementation errors.References
Thank you for considering this pull request. I'm open to feedback and willing to make further adjustments to ensure the documentation improvements align well with the project's standards and expectations.