- From: Lea Verou <notifications@github.com>
- Date: Wed, 15 Mar 2023 11:34:01 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 15 March 2023 18:34:13 UTC
> > Hi there, I know this is closed, but just a quick question wrt API design that I didn't see being brought up during the actual review: Why is this a set of global functions, instead of keyed off some kind of namespace? > > That was raised by me in [#390 (comment)](https://github.com/w3ctag/design-reviews/issues/390#issuecomment-668755957), and answered by a member of the Tag in the following comment. This was before my time, but IMO there should have been stronger guidance against this. It's not just about namespacing, I think it's more confusing for authors when functions are just added to the global scope like this, as there's nothing tying related parts of an API together. I guess this ship has sailed now, but I'll open a design principles issue so we can avoid it in the future. -- Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/390#issuecomment-1470562239 You are receiving this because you are subscribed to this thread. Message ID: <w3ctag/design-reviews/issues/390/1470562239@github.com>
Received on Wednesday, 15 March 2023 18:34:13 UTC