Consider a single default convention
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- julia
- Domain
- machine-learning
Research direction
No file, test, or implementation entry point is named; start by reading the issue discussion about DefaultConvention and CustomConvention. Review ScientificTypesBase.jl issue 21 only after the convention question is resolved. Done means reaching a decision on whether multiple conventions should remain supported, with the resulting scope made explicit.
Written by the indexing model from the issue text.
Description
I am genuinely interested in learning about the use cases of custom conventions. Do you have practical use cases where users needed to customize the default convention? What is the value of having multiple conventions? Does it actually help the community converge into something? My impression is that everyone is using DefaultConvention and we are maintaining code that is unnecessarily complex with support for multiple conventions. If a package A relies on DefaultConvention and package B relies on CustomConvention, what happens? Do we really want to support such use cases?
Appreciate if you can clarify these questions. I can help with https://github.com/JuliaAI/ScientificTypesBase.jl/issues/21 after this is sorted out. My personal opinion is that we should not waste time modeling multiple conventions and should ask the community to adhere to a single convention for scientific types. It has tremendous benefits in more complex pipelines.
- Dominant language
- Julia
- Stars
- 99
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from JuliaAI/ScientificTypes.jl
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
JuliaAI/ScientificTypes.jl#204 · 1 comment ·
-
next breaking release
Difficulty 5/5 Over a week Newbie friendliness 20/100
JuliaAI/ScientificTypes.jl#195 ·
-
next breaking release
Difficulty 5/5 Over a week Newbie friendliness 25/100
JuliaAI/ScientificTypes.jl#194 · 4 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
JuliaAI/ScientificTypes.jl#192 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
JuliaAI/ScientificTypes.jl#182 · 3 comments ·
All issues in JuliaAI/ScientificTypes.jl
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Sienna-Platform/PowerSimulations.jl#1737 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
FluxML/Optimisers.jl#254 ·
-
Minor: floodplain warning percentage, scalar output error message and a never-true identity checkOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JuliaAI/MLJTransforms.jl#101 ·
Maintainers usually reply within 1 day
-
@contents blocks fail to render on Julia 1.14Possibly taken @sbfnk claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
LuxDL/DocumenterVitepress.jl#410 ·