Fix metadata loading upon `Resource.objects()`

Since !12 (closed) is most probably not enough, I now simply allow for the new pattern to match.

I think this is superfluous now - the metadata duplicates seem to have vanished and I just added your f"/{path}/@type=metadata" in key to the method, with a minor adjustment of quoting the path, because certain symbols outside of ascii range needed to be escaped.

Yes, I saw your changes on the master :) and I just did not stop to close this PR xD Thanks for fixing the issue! One thing - I would like to see also your changes go through a PR, i.e. to come from an development branch and to be merged in. This way, I am 1) alerted before changes are merged and later released and 2) it is easier to follow what has changed. (The last diff looks like a full rewrite of the resource.py file)

I hope the last commits weren't a full rewrite of the resource.py file, because I just changed a few lines or so, but I think I can manage the additional work with the dev branch stuff (given that I don't forget about it). Time to follow "industry best practices" I guess... xD

No, I figured what lines actually had changes pretty fast (since I expected these lines to change ) I do not know why they all got marked here in the diff... Thanks a lot for considering :) One big advantage: on your private dev branch force push is not a problem

Finally! Force pushing to master without consequences! My dreams have come true!

closed