Skip to content

Conversation

@dclaux
Copy link
Member

@dclaux dclaux commented Jul 10, 2019

dclaux and others added 30 commits May 29, 2019 14:36
 - adaptivecards-controls@0.3.0
 - adaptivecards-data@0.1.0-alpha1
 - adaptivecards-designer-app@0.2.1
 - adaptivecards-designer@0.7.0
 - adaptivecards-site@0.4.1
 - hexo-theme-adaptivecards@0.1.1
 - adaptivecards-visualizer@1.2.1
 - adaptivecards@1.3.0-alpha1
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
Copy link

@shalinijoshi19 shalinijoshi19 left a 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.

Copy link
Member

@paulcam206 paulcam206 left a 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;
Copy link
Member Author

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)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed

@shalinijoshi19
Copy link

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!

@shalinijoshi19
Copy link

shalinijoshi19 commented Aug 28, 2019

Are you able to update the description to be more descriptive? Thanks

@shalinijoshi19
Copy link

shalinijoshi19 commented Aug 28, 2019

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

@dclaux
Copy link
Member Author

dclaux commented Aug 28, 2019

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:

  • One to allow a fully functional implementation of the version selector in the designer (an issue has already been raised for that feature: [Designer] Version Restriction #3260)
  • One to cleanup the parsing path in the renderer, which will likely be necessary for logging once we all agree on what needs to be logged

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.

@shalinijoshi19
Copy link

shalinijoshi19 commented Aug 28, 2019

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:

  • One to allow a fully functional implementation of the version selector in the designer (an issue has already been raised for that feature: [Designer] Version Restriction #3260)
  • One to cleanup the parsing path in the renderer, which will likely be necessary for logging once we all agree on what needs to be logged

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.

@dclaux
Copy link
Member Author

dclaux commented Aug 28, 2019

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.

@shalinijoshi19
Copy link

shalinijoshi19 commented Aug 28, 2019

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.

  1. Fixing up the usage of the Fixes keyword to enable the github auto-closure logic to run
  2. Is there a way for each that you can summarize what was broken ? The code changes would typically reflect how you fixed it, but not necessarily what was broken, which is where the description helps. If you noticed the template, there was a link that went at length if you wanted to read up but that;s more for reference really _(it helps with this and potential reverts should they be needed at any point, if we can avoid bundling in too many disparate changes in one PR/commit) _
  3. How Verified looks OK to me.

@shalinijoshi19
Copy link

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).

@dclaux
Copy link
Member Author

dclaux commented Aug 28, 2019

I have updated to uses the proper "fixes" syntax
The issues already describe what was broken, what else would you like to see in this PR?

@dclaux
Copy link
Member Author

dclaux commented Aug 28, 2019

All my changes are unrelated to the UWP renderer and do not touch its codebase. I am ignoring the failure for that reason.

@dclaux dclaux merged commit 1f534d6 into master Aug 28, 2019
@dclaux dclaux deleted the clean-template-engine-branch branch August 28, 2019 22:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

5 participants