Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-20350] Windows: Update parity report generation/docs to show support for missing items

GitHub Issuen/a
TypeStory
PriorityHigh
StatusClosed
ResolutionDone
Resolution Date2016-08-04T02:44:25.000+0000
Affected Version/sn/a
Fix Version/sRelease 5.4.0
ComponentsWindows
Labelsn/a
ReporterChristopher Williams
AssigneeChristopher Williams
Created2016-02-04T17:16:05.000+0000
Updated2018-10-10T16:30:04.000+0000

Description

I'm not sure if this is a doc issue or a problem with the scripts we use to generate the parity report. In any case, looking at http://builds.appcelerator.com/mobile/master/mobilesdk-6.0.0.v20160203193439-parity.html I'm seeing some APIs listed as unsupported though they really are: - Global - Modules.Cloud* (?) - Titanium.BlobStream - Titanium.BufferStream - Titanium.Filesystem.FileStream - Titanium.Map - Titanium.Map.Annotation - Titanium.Map.View - Titanium.Module - Titanium.Proxy - Titanium.UI.AttributedString - Titanium.UI.ListItem - Titanium.UI.ListSection - Titanium.UI.Picker - Titanium.XML.CDATASection - Titanium.XML.Comment - Titanium.XML.DocumentFragment - Titanium.XML.EntityReference - Titanium.XML.Text

Comments

  1. Christopher Williams 2016-02-04

    cc [~kota] [~gmathews] [~bimmel]
  2. Gary Mathews 2016-02-09

    PR: https://github.com/appcelerator/titanium_mobile_windows/pull/554
  3. Christopher Williams 2016-02-11

    [~gmathews] Seems like only some of this "worked". (just the stream classes?) These are all still showing as NO for http://builds.appcelerator.com/mobile/master/mobilesdk-6.0.0.v20160211081637-parity.html - Global - Modules.Cloud* (?) - Titanium.Map - Titanium.Map.Annotation - Titanium.Map.View - Titanium.Module - Titanium.Proxy - Titanium.UI.AttributedString - Titanium.UI.ListItem - Titanium.UI.ListSection - Titanium.UI.Picker - Titanium.XML.CDATASection - Titanium.XML.Comment - Titanium.XML.DocumentFragment - Titanium.XML.EntityReference - Titanium.XML.Text
  4. Gary Mathews 2016-02-12

    I notice that too, I'll take a look as to why that is happening.
  5. Gary Mathews 2016-02-18

    PR: https://github.com/appcelerator/titanium_mobile_windows/pull/564
  6. Kota Iguchi 2016-02-24

    [~gmathews] Is this considered to be "fixed" by PR 564?
  7. Christopher Williams 2016-02-24

    [~kota][~gmathews]I'm still seeing gaps in the parity report where we have classes but say we don't: http://builds.appcelerator.com/mobile/master/mobilesdk-5.4.0.v20160224050025-parity.html - Titanium.UI.Picker - Titanium.UI.ListItem - Titanium.UI.AttributedString - Titanium.Map - Titanium.Map.Annotation - Titanium.Map.View
  8. Gary Mathews 2016-02-28

    [~cwilliams] Yes, this is because of http://studio-jenkins.appcelerator.org/job/titanium_mobile_windows_master/ not pulling the repository correctly. http://studio-jenkins.appcelerator.org/job/titanium_mobile_windows_master/634/console Shows that .yml files for those classes are not generated. Once that has been fixed this issue can be resolved. I would take a look myself, but I don't have access to the build server. The windowsphone percentage in the parity report should be ~38%
  9. Christopher Williams 2016-04-20

    Looks like this is some weird build server issue. The build is checking out the correct revision of the repo, but is not generating all the xml files we expect. I logged in and manually ran and saw the same odd behavior. I wiped the workspace and still saw the behavior. So now, I'm looking to see if maybe an outdated node is the cause of the issue on that machine? Its on an ancient v0.10.13 build. I'm grabbing v4.4.3 now.
  10. Ewan Harris 2016-07-15

    [~cwilliams] The parity report still appears to be missing the following from your comments: * Titanium.UI.ListItem * Titanium.UI.AttributedString * ti.cloud module Should I close this ticket and open a new one to address these?

JSON Source