-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Style Guide v1 #253
Style Guide v1 #253
Conversation
# Conflicts: # docs/resources/data-representation/global-properties.md
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@PoojaB26 some nit changes. Also, how about if we mention somewhere on the naming convention for custom functions and actions?
What do you mean by actions here? Just for action block names? bc otherwise actions dont have names right? |
Co-authored-by: pinkeshmars <[email protected]>
No, I meant the naming convention for writing custom functions and custom actions in custom code, such as using 'lowerCamelCase.' However, this page primarily focuses on variables rather than method names. Perhaps we could add a small note or piece of information about it for clarity. |
Got it! Yes added a section for functions too. |
Description
Provide a brief overview of what this documentation update is about. Explain what sections or topics are being added or revised.
Linear ticket and magic word Fixes DEVR-24
Type of change