On Wed Dec 6 17:55:09 2023 +0000, Jacek Caban wrote:
C stubs are generally fine, but I don't think that exposing them to JS right away is a good idea. Web pages can often deal with missing properties, while providing stubs like that will just throw an error. There is no strict rule when to expose new interfaces, I usually did that together with at least a partial implementation of the interface (which also meant that I had a use case requiring that). Anyway, a few days before the code freeze does not feel like a good moment for exposing a bunch of stubs to JS, I'd suggest to add only C stubs for now.
Good point (honestly errors are way easier to debug, but before code freeze is definitely a bad idea as you said). Also for the future, I should actually reverse the order of the tids since otherwise they don't even become writable due to same name existing.