1170709 - [Compat Data][Importer] Parse CompatNightly

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: General, defect)

Description

[Florian Scholz (Open Web Docs)]

What did you do?
================
1. Looked at https://browsercompat.herokuapp.com/importer/4720 and others.
2. 
3. 

What happened?
==============
{{CompatNightly}} is not parsed.

What should have happened?
==========================
Import the version as "nightly" or "future release" for this feature.

Is there anything else we should know?
======================================
We have a lot of documented things that are available in the Firefox Nightly channel only. Is there another way to fix these import parsing errors?

Comment 1

[Florian Scholz (Open Web Docs)]

The macro has a parameter, btw.
E.g. {{CompatNightly("firefox")}}
See https://developer.mozilla.org/en-US/docs/Template:CompatNightly

Comment 2

[John Whitlock [:jwhitlock]]

I think Firefox Nightly would be version=null, status=beta.  This probably requires the API changes in bug 1160214 (Support unknown future versions) before the scraper can support it.

Comment 3

[John Whitlock [:jwhitlock]]

fsholz: what is the difference between CompatNightly("firefox") and Firefox 42?  Could instances of CompatNightly all be replaced by specific future version numbers?

Comment 4

[Florian Scholz (Open Web Docs)]

> fscholz: what is the difference between CompatNightly("firefox") and Firefox
> 42?  

Some experimental features are only appearing in the Nightly version of Firefox. It is basically a flag depending on the "train". These features will stay in Nightly and are not riding the train into beta or release version of Firefox. Every 6 weeks versions are bumped. The Nightly-only features stay in Nightly with the new version. The version of Nightly is not really important. We refer to it as "Nightly" without a version.

> Could instances of CompatNightly all be replaced by specific future version numbers?
No.

Comment 5

[John Whitlock [:jwhitlock]]

Code to handle {{CompatNightly}} is submitted in PR #41:

https://github.com/mozilla/web-platform-compat/pull/41

It becomes a Version resource with version="nightly" and status="future".

The subject page now imports cleanly:

https://browsercompat.herokuapp.com/importer/4720

I haven't run a full reparse of all the imported pages, just that one.

Comment 6

[MDN Team (:mdn-dev)]

Commits pushed to master at https://github.com/mozilla/web-platform-compat

https://github.com/mozilla/web-platform-compat/commit/71b7c960a60b055b12db71bf48aa453d436b59ab
bug 1170709 - Add --skip-deletes option

For tools/load_spec_data.py, if a Maturity becomes unused, the default
is to delete it.  The --skip-deletes option syncs additions and changes
but not deletes.

https://github.com/mozilla/web-platform-compat/commit/2a643f726fb63b6a353f25ac5b9df3328bc95fb3
fix bug 1170709 - {{CompatNightly}} and others

When scraping compatibility cells, {{CompatNightly}} is translated into
a version with version "nightly" and status "future".  Also, other
KumaScript such as {{CompatNo}} is translated into the new "unknown
version" with version "current" and status "current".