Comments (7)
@caridy You mentioned there were other gaps in engine.d.ts. Can we merge this with that issue or repurpose this to cover it all?
from lwc.
The idea is to eliminate engine.d.ts
as a manual file, and produce one as part of the build process. @rsalvador and I decided to keep this around because it was easier, but right after the next cut, we should remove that.
The concern is mostly that a generated file will contain everything, while devs will only have access to some things, other are meant to be used for other tools (e.g.: Aura), and we haven't found an easy way to have that split in the types as well.
from lwc.
For the lwc-language-service we will also need an updated engine.d.ts for 214
from lwc.
Here I was adding a missing method: #60
After that I did look a little into how to generate the engine.d.ts automatically but it did look pretty complicated to generate the equivalent of engine.d.ts
from lwc.
Is this still an issue @rsalvador @kevinv11n ?
from lwc.
We can close this, the wire def was updated here: a091304
from lwc.
Config bag needs to be optional. I'll issue a PR shortly.
from lwc.
Related Issues (20)
- List re-rendering causes DOM state to be lost HOT 1
- Type definition for `createElement` is inaccurate
- Remove temporary support for v7 compiler + v6 engine
- Synthetic custom element lifecycle swallows DOM errors for `insertBefore` HOT 1
- Multiple Off-Platform LWC's on one page HOT 9
- array mutations are not reactive in a custom lightning-datatable component. HOT 2
- Add Karma fuzz-testing for mixed API version components HOT 1
- `disableSyntheticShadowSupport` should allow `<slot>`s to be static-optimized
- Remove `validationOptOut` for manual opt-outs of hydration mismatch validation HOT 1
- Upgrade to prettier v3
- Log warning for host mutation during SSR HOT 1
- Maintaining the Id Attributes after component render. HOT 2
- Remove remaining vestiges of `jest` types
- `lwc:spread` applies props rather than attributes
- Migrate from yarn to pnpm HOT 2
- Remove misleading warning when using `@wire` on a getter or a setter HOT 1
- Consider removing `setHooks`
- Light DOM slot forwarding fails to render for duplicated slot names HOT 1
- `@wire` on getter/setter ignores implementation
- Synthetic shadow + duplicate slots + slot forwarding: `Failed to execute 'removeChild' on 'Node'`
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from lwc.