Grigas
Grigas
Another fix was released with `4.6.2`, closing the issue for now - please re-open if you can still reproduce the problem after consuming the new version.
As far as I can tell, E2E tests found 2 problems in the tree widget: - `tw-tree-renderer` needs `{ height: "100%" }`. - Node widths are incorrect - that's clearly...
> I'll have to disagree there, if you create a major each time you require newer peer dependency, we'll end up with version 125.10.96 within 2 year... > > Any...
> I'm being confirmed by @calebmshafer that this is how we want to go, so be it. Can't wait to see the results. You don't need to bump peer dependencies...
Related: https://github.com/iTwin/iTwinUI/issues/2112
`@itwin/[email protected]` release has the fix: https://github.com/iTwin/iTwinUI/releases/tag/%40itwin%2Fitwinui-react%403.16.0. Need to bump the dependency and confirm.
In our new packages we're trying out an approach to not export such types, e.g.: ```ts /** not exported at all */ interface MyProps { someProp: number } /** not...
BTW, I think the problem of not being able to modify props-only or return-only interfaces in a non-breaking way is separate from the exported `@internal` APIs problem. Regarding the latter,...
> If they do this and you later add a new required property to `MyReturnType`, you will break their code. Not unless they're creating instances of `MyFunctionReturnType` or implementing it....
> > our function returns an object that doesn't have a public type > > How is anybody supposed to use your API if they can't know anything about its...