|
| 1 | +# 2024-04-01 |
| 2 | + |
| 3 | +Note Taker: Chris Manson |
| 4 | +Time Keeper: Chris Manson |
| 5 | + |
| 6 | +## Attendees |
| 7 | + |
| 8 | +Add yourself to the list if you attend and check the box! |
| 9 | + |
| 10 | +- [x] Ed Faulkner (EF) |
| 11 | +- [x] Chris Manson (CM) |
| 12 | +- [ ] Aaron Chambers (AC) |
| 13 | +- [x] Alex (A) |
| 14 | +- [x] Preston Sego (PS) |
| 15 | +- [x] Simon Ihmig (SI) |
| 16 | +- [ ] Katie Gengler (KG) |
| 17 | +- [ ] Peter Meehan (PM) |
| 18 | +- [ ] Krystan HuffMenne (KH) |
| 19 | +- [x] Peter Wagenet (PW) |
| 20 | +- [ ] James Davis (JD) |
| 21 | +- [x] David Taylor |
| 22 | +- [x] Johnard |
| 23 | +- [x] Tommyjr |
| 24 | + |
| 25 | +## Topics |
| 26 | + |
| 27 | + |
| 28 | + |
| 29 | +### Should @ember/test-helpers, @ember/test-waiters, be put in ember-source? <@NullVoxPopuli> |
| 30 | + |
| 31 | +- Test-helpers, specifically, relies on private APIs |
| 32 | +- EF: what are we being using |
| 33 | +- PS: we are using things like setOnError |
| 34 | +- EF: is the need for this because we don't have setComponent |
| 35 | +- I would prefer to stabilise the apisthat are being used |
| 36 | +- (discussion of what the actual things are) |
| 37 | +- EF: a lot of the examples are things that are on the way out |
| 38 | +- we could just wait and remove them when they're not being used any more |
| 39 | + |
| 40 | + |
| 41 | +### what should happen with https://github.com/emberjs/ember-test-helpers/pull/1528 <@NullVoxPopuli> |
| 42 | + |
| 43 | +- EF: looks good |
| 44 | +- we need to fix the conflict to continue |
| 45 | +- |
| 46 | + |
| 47 | +### A new attempt at my strategy of splitting ember-cli and the blueprint system: https://github.com/ember-cli/ember-cli/pull/10671 <@mansona> |
| 48 | + |
| 49 | +- (long discussion about the strategy) |
| 50 | +- EF: we can do this but don't change behaviour i.e. don't resolve from cwd |
| 51 | +- most of what ember-try's complexity is around local running and trying to support monorepos, which have seemingly unlimited configuration issues |
| 52 | + |
| 53 | +### Non-monorepo V2 addon with ember test matrix example <@ef4> |
| 54 | + |
| 55 | +- example: |
| 56 | + - https://github.com/ef4/memory-scroll/ |
| 57 | + - https://github.com/embroider-build/try |
| 58 | + |
| 59 | +- EF: looking for feedback for people who are using ember-try |
| 60 | +- KG: bert has been working on upgrading ember-try it would be great if we could chat to him about rolling this in |
| 61 | +- (discussion about ember-try running your package manager for you) |
| 62 | +- |
| 63 | + |
| 64 | +<5 mins> Should content-tag-utils be in an org managed by the tooling team? https://github.com/NullVoxPopuli/content-tag-utils <@mansona> |
| 65 | +<10 min> Glint declarations issue <@ef4> |
| 66 | +<5 mins> Template-tag codemod custom resolver https://github.com/embroider-build/embroider/pull/2419 <@davidtaylorhq> |
| 67 | + |
| 68 | + |
0 commit comments