Sergey Danilchenko

> @daniser can you give me permissions to push to this PR branch please? @bakerkretzmar No problem. Check it out, I think I done it right.

> This is cool, thanks! I agree we should handle this more like Laravel's route helper does, I'm not sure yet how I feel about doing anything _more_ than that....

A quick search on Laravel codebase inside `Illuminate\Routing` namespace with keywords "fragment", "anchor", "hash" hasn't given any results except aforementioned `RouteUrlGenerator::addQueryString` method. As for `route().current()`. I have an UI tab...

@bakerkretzmar Ok, I'll do that. Should I keep `_fragment` magic key when passing parameters using object or do you have better alternatives in mind?

> I should have been more specific ... I only tested with Firefox 😅 I forgot to test it with browsers at all😁

I have same issue with unregistered axios instance. However, I'm using custom repository: ```ts export default class MessageRepository extends AxiosRepository { use = Message; fetch = async (roomId: string) =>...

Thanks, it worked! Strangely, this part wasn't needed (probably due to generic signature of `useRepo`?): > And if you use typescript also add this to your own `types/pinia-orm.ts`: > >...

@annymosse You are probably using `"moduleResolution": "node"` in your `tsconfig.json` file. It's deprecated and causes various resolution problems in modern code. Please check out [this discussion](https://github.com/CodeDredd/pinia-orm/pull/1681#issuecomment-1724186687).

@chriscant downgrading `node-ignore` worked for me. Add this entry into your `package.json`: ```json "resolutions": { "ignore": "4.0.6" }, ``` As alternative, try using case-sensitive current path (including capital drive letter)....

We can add boolean flag to control behaviour and keep this feature in v4.0. What do you think? `ArrayAccess` is indeed needed, as `mapArray` uses it to set values. `Traversable`...