Skip to content
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

Add BrowserFeatureSupportEvents table #865

Merged
merged 1 commit into from
Nov 5, 2024

Conversation

jcscottiii
Copy link
Collaborator

@jcscottiii jcscottiii commented Nov 4, 2024

This table logs when any browser is released. Then it records whether or not that the feature is supported. This is useful because the missing one implementation calculation occurs when another browser is released and not the target browser itself.

Fixes: #833

Is a split up of https://github.com/GoogleChrome/webstatus.dev/compare/missing-one-impl-count-db?expand=1

This table logs when any browser is released. Then it records whether or
not that the feature is supported. This is useful because the missing
one implementation calculation occurs when another browser is released
and not the target browser itself.

Fixes: #833
jcscottiii added a commit that referenced this pull request Nov 5, 2024
Depends on: #865

This method is the entrypoint to calculate the events stored in the BrowserFeatureSupportEvents table introduced in #865.

It reads all of the web features, browser releases and feature availabilities. With that, it builds the event log.

In order to read all that data, small helper methods were created to assist.

This PrecalculateBrowserFeatureSupportEvents method does not take in any input and just uses existing table data.

Fixes #834
jcscottiii added a commit that referenced this pull request Nov 5, 2024
Depends on: #865

This method is the entrypoint to calculate the events stored in the BrowserFeatureSupportEvents table introduced in #865.

It reads all of the web features, browser releases and feature availabilities. With that, it builds the event log.

In order to read all that data, small helper methods were created to assist.

This PrecalculateBrowserFeatureSupportEvents method does not take in any input and just uses existing table data.

Fixes #834
@jcscottiii jcscottiii added this pull request to the merge queue Nov 5, 2024
Merged via the queue into main with commit 18accba Nov 5, 2024
6 checks passed
@jcscottiii jcscottiii deleted the jcscottiii/add-events-table branch November 5, 2024 21:58
jcscottiii added a commit that referenced this pull request Nov 5, 2024
Depends on: #865

This method is the entrypoint to calculate the events stored in the BrowserFeatureSupportEvents table introduced in #865.

It reads all of the web features, browser releases and feature availabilities. With that, it builds the event log.

In order to read all that data, small helper methods were created to assist.

This PrecalculateBrowserFeatureSupportEvents method does not take in any input and just uses existing table data.

Fixes #834
github-merge-queue bot pushed a commit that referenced this pull request Nov 5, 2024
Depends on: #865

This method is the entrypoint to calculate the events stored in the BrowserFeatureSupportEvents table introduced in #865.

It reads all of the web features, browser releases and feature availabilities. With that, it builds the event log.

In order to read all that data, small helper methods were created to assist.

This PrecalculateBrowserFeatureSupportEvents method does not take in any input and just uses existing table data.

Fixes #834
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Design Spanner schema for "Missing One Implementation" count
2 participants