Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.
Please ensure you have read and noticed the checklist below.
Checklist
Put an x in the boxes that apply. If you're unsure about any of them, don't hesitate to ask. We are here to help!
This is simply a reminder of what we are going to look for before merging your code.
[x] I have read and noticed the CONTRIBUTING document
[x] I have added necessary documentation or screenshots (if appropriate)
[x] I have tested my changes or additions for proper functionality.
[x] I have followed, as best as possible, the same function layout and coding style of other existing functions/code.
Types of changes
Please check x the type of change your PR introduces:
[ ] Bugfix (change which fixes an issue)
[ ] Feature (change which adds functionality)
[x] Code style update (formatting, renaming)
[x] Refactoring (functional, structural)
[x] Documentation content changes
[ ] Other (please describe)
** |-->:
What is the current behavior?
Please describe the current behavior that you are modifying, or link to a relevant issue.
** |-->:
Constants in LibreOffice_Constants were unordered and hard to find.
Constants $LOW_FIELDADVTYPE were not named the same as the other Field Type Constants,
$LOW_FIELDDOCINFO
$LOW_FIELDTYPE
What is the new behavior?
Please describe the behavior or changes that are being added by this PR.
** |-->:
Constants are now alphabetically sorted.
$LOW_FIELDADVTYPE are now named in the same format,
$LOW_FIELD_ADVTYPE
Influences and relationship to other functionality
Describe how the changes will affect other functions, potential script breaking changes, etc.
** |-->:
If the renamed Constants change is accepted, this will break compatibility with Scripts created using previous versions of this UDF that used this constant.
Additional context
Add any other context about the problem here.
** |-->:
Pull request
Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request.
Please ensure you have read and noticed the checklist below.
Checklist
Put an
x
in the boxes that apply. If you're unsure about any of them, don't hesitate to ask. We are here to help!This is simply a reminder of what we are going to look for before merging your code.
Types of changes
Please check
x
the type of change your PR introduces:** |-->:
What is the current behavior?
Please describe the current behavior that you are modifying, or link to a relevant issue.
** |-->:
What is the new behavior?
Please describe the behavior or changes that are being added by this PR.
** |-->:
Influences and relationship to other functionality
Describe how the changes will affect other functions, potential script breaking changes, etc.
** |-->:
Additional context
Add any other context about the problem here.
** |-->:
System under test
Please complete the following information.