Linked data with polymorphism does not work with custom `key_type`
还没有人认领这个 Issue。
评估
调研方向
从 lib/jsonapi/resource_serializer.rb:464 开始检查 foreign_key_value，重点关注配置了自定义 key_type 时多态关系如何获取其 id。复现报告中的情况，并添加覆盖测试，展示序列化关系的 id 遵循自定义 key_type，而不是始终使用直接的关联 id。
由索引模型根据 Issue 内容生成。
描述
This issue is a (choose one):
- Problem/bug report.
- Feature request.
- Request for support. Note: Please try to avoid submitting issues for support requests. Use Gitter instead.
Checklist before submitting:
- I've searched for an existing issue.
- I've asked my question on Gitter and have not received a satisfactory answer.
- I've included a complete bug report template. This step helps us and allows us to see the bug without trying to reproduce the problem from your description. It helps you because you will frequently detect if it's a problem specific to your project.
- The feature I'm asking for is compliant with the JSON:API spec.
Description
If you create a polymorphic association with custom key_type id is always taken which leads to a wrong data sharing.
Bug reports:
Everything is on lib/jsonapi/resource_serializer.rb:464
When calling source.public_send("#{relationship.name}_id"), it is fine (faster) but it does not take care about custom key_type.
But if you call source.public_send(relationship.name).try(:id), you're using the custom key_type.
Features:
We can set another argument to has_one to be able to mention that the key_type has been modified.
Here is my proposition:
# app/resources/my_awesome_resource
has_one :positionable, polymorphic: true, foreign_key: :positionable_id, foreign_key_type_changed: true
# jsonapi/resource_serializer.rb
def foreign_key_value(source, relationship)
# If you have changed the key_name, don't even try to look at `"#{relationship.name}_id"`
# just load the association and call the custom key_name
foreign_key_type_changed = relationship.options[:foreign_key_type_changed] || false
related_resource_id =
if source.preloaded_fragments.has_key?(format_key(relationship.name))
source.preloaded_fragments[format_key(relationship.name)].values.first.try(:id)
elsif !foreign_key_type_changed && source.respond_to?("#{relationship.name}_id")
# If you have direct access to the underlying id, you don't have to load the relationship
# which can save quite a lot of time when loading a lot of data.
# This does not apply to e.g. has_one :through relationships.
source.public_send("#{relationship.name}_id")
else
source.public_send(relationship.name).try(:id)
end
return nil unless related_resource_id
@id_formatter.format(related_resource_id)
end
- 主要语言
- Ruby
- 星标
- 2.3k
- 派生
- 546
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
我们还没有检查这个项目的环境配置文件。先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
JSONAPI-Resources/jsonapi-resources 的其他 Issue
-
难度 1/5 1 小时以内 新手友好度 85/100
-
难度 3/5 1-2 天 新手友好度 50/100
JSONAPI-Resources/jsonapi-resources#1488 · 1 条评论 ·
-
难度 4/5 3-5 天 新手友好度 42/100
JSONAPI-Resources/jsonapi-resources#1479 · 2 条评论 ·
-
难度 4/5 3-5 天 新手友好度 30/100
JSONAPI-Resources/jsonapi-resources#1477 · 3 条评论 · 1 个 reaction ·
-
难度 3/5 1-2 天 新手友好度 45/100
查看 JSONAPI-Resources/jsonapi-resources 的全部 Issue
相似的 Issue
-
P2 testing
难度 1/5 1 小时以内 新手友好度 90/100
维护者通常 1 天内回复
-
performance
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
openSUSE/open-build-service#20338 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
バグ
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复