[
https://issues.apache.org/jira/browse/BEAM-10309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17183461#comment-17183461
]
Beam JIRA Bot commented on BEAM-10309:
--------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> Reorganize Go coder packages.
> -----------------------------
>
> Key: BEAM-10309
> URL: https://issues.apache.org/jira/browse/BEAM-10309
> Project: Beam
> Issue Type: Improvement
> Components: sdk-go
> Reporter: Daniel Oliveira
> Assignee: Daniel Oliveira
> Priority: P4
> Labels: stale-assigned
>
> Context is in the comments here: https://github.com/apache/beam/pull/12059
> "As an aside, and not in this PR, what do you think about refactoring the
> locations of all the coder code in the SDK right now. I noticed while trying
> to figure out how to make some coders that its very unintuitive trying to
> figure out how to make coders for certain types (for example ints). Right now
> it seems like built-in coders are all in graph/coder and custom coders for Go
> types are in runtime/coderx."
> This would probably involve moving code from coderx into a more intuitive
> directory/package. Maybe something like graph/coder/custom, putting it as a
> subdirectory to the built-in coders. This would almost definitely need to
> wait until a major version update so we don't impact users that are using
> these packages already.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
