-
Notifications
You must be signed in to change notification settings - Fork 593
More designer fixes #3169
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
More designer fixes #3169
Conversation
Opportunistic small bug fixes
[Designer] Basic property categorization in property sheet
- adaptivecards-controls@0.3.0 - adaptivecards-designer-app@0.2.1 - adaptivecards-designer@0.7.0 - adaptivecards-site@0.4.1 - hexo-theme-adaptivecards@0.1.2 - adaptivecards-templating@0.1.0-alpha.0 - adaptivecards-visualizer@1.2.2 - adaptivecards@1.3.0-alpha1 - spec-generator@0.5.1 - typed-schema@0.5.1
shalinijoshi19
left a comment
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.
Could you please create specific topic branches for the changes here - One is sufficient but this is ulling in reviews and commits from a now committed set of changes which is confusing to review. Thanks. Please reach out to @paulcam206 for help.
paulcam206
left a comment
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.
per meeting review, this is approved pending the one outstanding issue found.
| } else { | ||
| } | ||
| else if (typeof value === "number") { | ||
| return value ? value : defaultValue; |
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.
Shouldn't be necessary? Value is a number at this point and therefore can be returned (0 is meaningful)
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.
Fixed
|
Hi David, In general do you have a list of known cleanup/refactoring in the codebase that you are working on or planning to work on at all? If there is could you let me know the issue# (all-up issue fine) for that? Also some of these might be able to be found and potentially fixed with a linter (es-lint) so we can potentially resolve any existing issues once we enable a linting tool for the codebase. Thanks! |
|
Are you able to update the description to be more descriptive? Thanks |
|
For fixes syntax, i believe you have to prefix each issue fixed with a keyword (eg fixes #<>, fixes #<> or else the issues themselves dont get auto-closed. Please refer to https://help.github.com/en/articles/closing-issues-using-keywords#closing-multiple-issues |
|
There isn't such a list. There is an issue open to replace "var" with "let" pretty much everywhere, which I do opportunistically (no real reason to address it all at once.) There will be one (or two) big refactors needed to enable additional features going forward:
I do not know when I'll be able to do these though. The first one is a large amount of work and is risky. |
Ok thanks. This is good to know and helpful context. Hooking up a linter should help clean up low hanging fruit like var usage I am hoping. |
|
The description is accurate, I list the issues that this PR fixes. Is there something else you'd like in there? I could describe what I actually did, but that'd be redundant with the code changes themselves. |
Yes please.
|
|
Btw, you may want to update from master to pull in the latest and greatest and verify things still look good (looks like your branch is out of date with master). |
|
I have updated to uses the proper "fixes" syntax |
|
All my changes are unrelated to the UWP renderer and do not touch its codebase. I am ignoring the failure for that reason. |
Major designer update, plus fixes for:
Verified manually.
Microsoft Reviewers: Open in CodeFlow