You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -90,7 +92,7 @@ Every section in the roadmap is accompanied by one or more issues. Contributions
90
92
Please see [contributing.md] for more details. If you just want to run the playground on your own machine, go to your terminal and enter the following commands:
Copy file name to clipboardExpand all lines: ROADMAP.md
+8-8Lines changed: 8 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -2,49 +2,49 @@
2
2
3
3
## Interactive HTML Preview
4
4
5
-
_Status: Shipped at May 23, 2020 ([#2](https://github.com/smeijer/testing-playground/issues/2))_
5
+
_Status: Shipped at May 23, 2020 ([#2](https://github.com/testing-library/testing-playground/issues/2))_
6
6
7
7
The html preview tab should be made interactive. In such a way that one can hover elements and see the recommended query. When clicking on the link, the query should applied to the editor, like the various query buttons do.
8
8
9
9
## Update Readme.md
10
10
11
-
_Status: Shipped at May 25, 2020 ([#23](https://github.com/smeijer/testing-playground/pull/23))_
11
+
_Status: Shipped at May 25, 2020 ([#23](https://github.com/testing-library/testing-playground/pull/23))_
12
12
13
13
We don't have any instructions on how to get the thing started at localhost, or how to contribute. This should be made crystal clear.
14
14
15
-
_Status: Shipped at May 24, 2020 ([#14](https://github.com/smeijer/testing-playground/issues/4))_
15
+
_Status: Shipped at May 24, 2020 ([#14](https://github.com/testing-library/testing-playground/issues/4))_
16
16
17
17
Also, I have no idea how it works, but I know we need to use emoji-key to list contributors in the readme. Is that an automated thing?
A [testing-playground.com] without tests... I don't think that should be a thing, but at this moment it is.
24
24
25
25
We should fix that, and use jest & testing-library to do it.
26
26
27
27
## Usage instructions
28
28
29
-
_Status: In backlog ([#8](https://github.com/smeijer/testing-playground/issues/8))_
29
+
_Status: In backlog ([#8](https://github.com/testing-library/testing-playground/issues/8))_
30
30
31
31
Do we need some instructions on how to use the tool? I'm not sure about this yet, but if we do, it should be added to the playground itself. Not just a markdown on github.
32
32
33
33
## Embeddable
34
34
35
-
_Status: Shipped at May 28, 2020 ([#9](https://github.com/smeijer/testing-playground/issues/9))_
35
+
_Status: Shipped at May 28, 2020 ([#9](https://github.com/testing-library/testing-playground/issues/9))_
36
36
37
37
How awesome would it be if we had an embed-mode, so users can embed the playground in the blogs they write about testing / testing-library?
38
38
39
39
## Support User-Event
40
40
41
-
_Status: In backlog ([#10](https://github.com/smeijer/testing-playground/issues/10))_
41
+
_Status: In backlog ([#10](https://github.com/testing-library/testing-playground/issues/10))_
42
42
43
43
I haven't worked out the details, but enabling users to play with [user-event]s would awesome. Perhaps together with adding support for [HTML mixed mode]?
44
44
45
45
## DevTools!
46
46
47
-
_Status: In progress ([#11](https://github.com/smeijer/testing-playground/issues/11))_
47
+
_Status: In progress ([#11](https://github.com/testing-library/testing-playground/issues/11))_
48
48
49
49
I believe we can wrap this project into a chrome extension. That way people can use the thing on their own sites, without needing to copy / paste html fragments. How awesome would that be?!
0 commit comments