Benjamin Rae

When you get that error you can merge with the `--allow-unrelated-histories` flag and then you just need to to resolve the conflicts.

Have you considered using a subdomain? That would make it `https://blog.xxx.com`. I see that pattern a lot more and I think it will be much easier to configure

Astro content supports remark and rehype plugins, there is a [remark-admonitions](https://github.com/elviswolcott/remark-admonitions) plugin but it doesn't seem to be maintained. You could try [remark-directive](https://github.com/remarkjs/remark-directive)

As far as I can see this use of `aria-label` is valid according to https://w3c.github.io/aria/#aria-label However as it says `title` may be preferred but would create a tooltip, or even...

Now that I'm more familiar with the repository I have had a look into what is causing this. In the function (checkDependencies)[https://github.com/loopbackio/loopback-next/blob/391c3158c3fecb17baf267a86c1b5a651b1f640c/packages/cli/lib/version-helper.js#L36] the project's dependencies are checked unless the command...

Have you tried defining properties as unique on the model? I believe you can do something like this, at least with Postgres, I don't know if it works in all...

This is the error that the CLI gives: ``` $ lb4 relation ? Please select the relation type belongsTo No change to package.json was detected. No package manager install will...

@loopback/boot is able to find artifacts in nested folders. I wonder if same type of artifact discovery could be used for @loopback/cli to find models/repositories in nested folders.

> I confirm lb4 is not able to find models in subdirectory. Not really a bug, but a nice to have feature. It could definitely make organization a lot easier...

Any updates on this? Or any help required? This is the only feature that is stopping me from leaving Postman behind and adopting Bruno