Rafael Pólit

We just fixed, in theory, that 200s that were wrongly reported should return 404s. Now they are apparently returning 301s? Maybe it's because it's the first param and it tries...

There should be two different validations: it needs to be EITHER a valid language, OR a valid URL endpoint. For example, `domain/en/entity` should, indeed, validate that `en` is a valid...

This could also happen if someone uses the API without the client. This needs to be validated for sure.

Just to clarify: all this process should be done in the relationships tab of the entity view. - Create two entities - Go into entity 1 and into it's relationships...

This is weird. I see no reason (not even on Text References) where changing the template would require deleting all relationships. But, as @fnocetti points out, this has been EXPLICITLY...

@fnocetti This precedes even our current HUB implementation. As you mention, there is no distinction between a relationship that was created via metadata, or via "standalone", nor there should be,...

@txau It’s a requirement for a lot of instances, so I sincerely hope we do. That is, we keep the metadata properties that are common to the previous and newly...

I'd like @daneryl or @konzz input on this. Yes, I believe its useful. But not on a 'prior template', 'new template' scenario. A simple sanitizing procedure that just strips the...

Our new agreement for flagging PRs is: - Draft: a work in progress not ready to be merged, usually no one does QA unless asked for - Non-draft: PR ready...

We are going for the long-term good solution here: changing templates never deletes connections, but sanitizes the metadata properly.