EdJoPaTo

> Edit after the CI reminded me: How to handle the code example in the docs which fails without the url feature? Yeah, I know. But I am not sure...

> A lot of the tests fail since the `url` dependency is optional, only enabled with `features = ["url"]` Maybe more details there: The `parse_url` method had a `#[cfg(feature =...

Uh, that is both smart and a simple solution! I like that! Have you checked out the rest of the improvements? Any thoughts on them?

> But I do think we should not be deprecating methods such as `new()` and `parse_url()` right away, this is just what I think. I like to have only one...

(Tried to solve merge conflicts and accidentally merged in main instead of master → rebased my changes to get rid of the wrong merge)

I just realized there is another `MqttOptions` for the v5 module. Also this PR is just ignored for months now. Not sure if there is any point in keeping it...

Additional to my last comment `MqttOptions` seems to have even more problems which should be refactored in my opinion. (See #434) As there need to be changes on a bigger...

I created the [wikibase-types](https://github.com/EdJoPaTo/wikibase-types) npm package for types returned by the wikibase / wikidata API. Its helpful but still not as good as a fully typed library. If someone has...

These compiler options only help, as far as i understand, to import things into your lib. The types have to be correct for that in the first place. (Correct me...

Updating the list on a regular basis would be a simple solution. But that also requires to update the projects depending on this library on a regular basis too. Updating...