Feature(s) impacted
Relationship between collections
Observed behavior
Lets take a collection Tag
which has only one field called name
as a non empty string,
and a collection Article
which has many Tag
.
When trying to access all the Article
records for a given Tag
record, a request is made to our backend with the name
value in the URL
Expected behavior
Any special character contained in the name
value should be encoded as they end up in the URL of the GET request made to our backend:
http://[…]/admin/forest/tag/NAME_VALUE_HERE/relationships/article/count?[…]
Failure Logs
Currently, if any name
value contains one of /\#%?
it will not be encoded and will cause various URL interpretation issues like 404 with some /
included as is.
I believe the URL building mechanism is set with IDs in mind, which usually don’t have any special character outside of -
, but this particular collection has no ID in our system and this is intended.
Context
- Project name: Inato Marketplace
- Team name: Inato
- Environment name: all
- Agent type & version: N/A
- Recent changes made on your end if any: N/A