-
Notifications
You must be signed in to change notification settings - Fork 8
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
Remove remaining deprecated apis #12
Conversation
Preview URLsGH Env: preview |
308f2b5
to
2911457
Compare
7f12f05
to
59487a3
Compare
59487a3
to
e46ce50
Compare
It would be nice if this managed to update with new commits. |
@@ -46,6 +47,9 @@ | |||
"plugins/sticky-columns": [ | |||
"./dist/plugins/sticky-columns/index.d.ts" | |||
], | |||
"plugins/row-selection": [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this something we manually have to add for each new plugin?
Maybe this should be a note in CONTRIBUTING
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's something that needs to be added in any package for any public entry point -- it's more "normal npm stuff", if that makes sense.
We probably should have a pointer to some doc talking about this tho.
@@ -0,0 +1,312 @@ | |||
import Component from '@glimmer/component'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why the *.gts
extension here? Is that this
Asking because I don't see other *.gts` files in the project, wondering if this is a new convention.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
all the rendering tests use gts.
Is that this
nay, it's this: https://rfcs.emberjs.com/id/0779-first-class-component-templates
"@glint/environment-ember-loose": "^0.9.5", | ||
"@glint/environment-ember-template-imports": "^0.9.5", | ||
"@glint/template": "^0.9.5", | ||
"@glint/core": "^0.9.6", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this version fixes some bugs I was working around, so I just upgraded to it
@@ -0,0 +1,12 @@ | |||
--- | |||
categoryOrder: 3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can now sort folders!
Finally green 🎉 |
this is probably where turbo might be useful, we can force the build of the addon before starting the app. |
But isn't this what It looks like |
what version of pnpm are you using? I have 7.13.4, and just upgraded to 7.13.6 |
pnpm --version Let me update |
Tried again with
Works for me now. |
```hbs template | ||
|
||
FPS: {{this.fps}}<br> | ||
<div data-container class="h-full overflow-auto" {{this.table.modifiers.container}}> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
come on, github. where's your syntax highlighting... :(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah, I noticed that, too. but that's likely my fault.
GitHub requires that at least 200 repos use a new syntax before they add highlighting for it -- and I don't think they've ever supported nested highlighting in markdown without "rendering the file"
|
||
import { headlessTable } from 'ember-headless-table'; | ||
import { RowSelection, toggle, isSelected, select, deselect } from 'ember-headless-table/plugins/row-selection'; | ||
import { DATA } from 'test-app/data'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh! that is goofy!
assert.expect(1); | ||
|
||
setupOnerror((error) => { | ||
let errorStr = error instanceof Error ? error.message : `${error}`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: I usually prefer String(error)
over ${error}
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why's that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tend to go by https://eslint.org/docs/latest/rules/no-implicit-coercion
To me, it's more clear that you're intending to coerce to a string if you say String(...)
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
legit, is it available in Eslint 7?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This rule was introduced in ESLint v1.0.0-rc-2.
await click(rows[0]); | ||
|
||
assert.strictEqual(ctx.selection.size, 0); | ||
assert.deepEqual([...ctx.selection.values()], []); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With so many assertions here, would it help to add failure messages? Otherwise it may be hard to keep track of what's failed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe -- I didn't have any issue debugging this when I wrote it though -- the contents of expected
and actual
are printed in the browser -- so it's fairly easy to see what's going on, imo.
(obvs, if I get confused later, messages will get added 😅 )
Co-authored-by: Dan Wenzel <[email protected]>
🎉 This PR is included in version 1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Requires: #11
Signature
interface instead of 4+ type arguments toBasePlugin
, which is more extensible, and maintainable long term, but has higher upfront cost for figuring out inference - extracted to Introduce plugin signatures #39