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.

Sign up for GitHub

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

Jump to bottom

Remove concrete reporting types from Reporting API spec #189

Closed
clelland opened this issue Dec 13, 2019 · 0 comments · Fixed by #190
Closed

Remove concrete reporting types from Reporting API spec #189

clelland opened this issue Dec 13, 2019 · 0 comments · Fixed by #190

Comments

@clelland
Copy link
Contributor

Following up on #169, three new repositories have been started at WICG for incubation and further discussion:

Crash reporting (spec)
Deprecation reporting (spec)
Intervention reporting (spec)

(I've installed myself as editor, more or less by default, but folks are more than welcome -- in fact encouraged -- to contribute.)

To close this up, we need to remove those report types from this repo, and ensure that all of the referenced terms are exported. (They probably should be in any case, so that other specs can define new report types as well.)
@clelland clelland mentioned this issue Dec 13, 2019
Merged
spaze added a commit to spaze/canhas.report that referenced this issue May 6, 2020
@spaze
Reporting API Editor's Draft has switched to structured headers (`Rep…
3c20ecf 
…orting-Endpoints`) and removed concrete types

w3c/reporting#197
w3c/reporting#189
spaze added a commit to spaze/canhas.report that referenced this issue May 6, 2020
@spaze
Reporting API Editor's Draft has switched to structured headers (`Rep…
094273d 
…orting-Endpoints`) and removed concrete types

w3c/reporting#197
w3c/reporting#189
spaze added a commit to spaze/canhas.report that referenced this issue May 6, 2020
@spaze
Reporting API Editor's Draft has switched to structured headers (`Rep…
4c31cfd 
…orting-Endpoints`) and removed concrete types

w3c/reporting#197
w3c/reporting#189
spaze added a commit to spaze/canhas.report that referenced this issue May 6, 2020
@spaze
Reporting API Editor's Draft has switched to structured headers (`Rep…
75c8fc9 
…orting-Endpoints`) and removed concrete types

w3c/reporting#197
w3c/reporting#189
spaze added a commit to spaze/canhas.report that referenced this issue May 7, 2020
@spaze
Reporting API Editor's Draft has switched to structured headers (`Rep…
bca2536 
…orting-Endpoints`) and removed concrete types

w3c/reporting#197
w3c/reporting#189
spaze added a commit to spaze/canhas.report that referenced this issue May 10, 2020
@spaze
Reporting API Editor's Draft has switched to structured headers (`Rep…
7febd3b 
…orting-Endpoints`) and removed concrete types

w3c/reporting#197
w3c/reporting#189
spaze added a commit to spaze/canhas.report that referenced this issue May 10, 2020
@spaze
Reporting API Editor's Draft has switched to structured headers (`Rep…
aea8cb3 
…orting-Endpoints`) and removed concrete types

w3c/reporting#197
w3c/reporting#189
spaze added a commit to spaze/canhas.report that referenced this issue May 16, 2020
@spaze
Reporting API Editor's Draft has switched to structured headers (`Rep…
9fc7359 
…orting-Endpoints`) and removed concrete types

w3c/reporting#197
w3c/reporting#189
spaze added a commit to spaze/canhas.report that referenced this issue May 21, 2020
@spaze
Reporting API Editor's Draft has switched to structured headers (`Rep…
2e25458 
…orting-Endpoints`) and removed concrete types

w3c/reporting#197
w3c/reporting#189
@jpchase jpchase mentioned this issue Aug 27, 2020
Open
@clelland clelland mentioned this issue May 30, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant
@clelland