-
Notifications
You must be signed in to change notification settings - Fork 7
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
Data type normalization (long-term effort) #86
Comments
17 tasks
Adding my observations here for inconsistent data types:
Other:
|
padmkris123
pushed a commit
that referenced
this issue
Dec 15, 2022
padmkris123
pushed a commit
that referenced
this issue
Dec 15, 2022
padmkris123
added a commit
that referenced
this issue
Dec 20, 2022
* new doc fixes * updating versions md * New API: window.Path * Fixing product name * Bumping package version number * removing TODO * removing extra uxp * Manually fixing issue #86 * Typos * Reverting changes * Addressing issue #86 and adding Object details * Add more description to Path.md * review comment - fixing space * Addressing review comments Co-authored-by: Padma Krishnamoorthy <[email protected]> Co-authored-by: Padma Krishnamoorthy <[email protected]>
Internal note: This now has a page on the internal wiki with best practices. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the UXP JS API references don't follow a standard when it comes to declaring data types. A few examples of various ways things are notated in the docs (and, "as the root", the corresponding JS type):
number
int
integer
number
Number
Integer
string
string
String
Promise<void>
void
)Promise
void
While this will be a big effort to fix, it currently
The text was updated successfully, but these errors were encountered: