Feature: consistent project names
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 712
- Forks
- 163
- PR merge metrics
- No merged PRs in 30d
Description
-
motivation: most SBT projects are ignorant of the eclipse environment,
in the sense, of how things are named in the workspace, and possible name conflicts -
for example
- scala-js https://github.com/scala-js/scala-js/issues/3176
- scala-native https://github.com/scala-native/scala-native/issues/1193
- this proposal is to implement better name policy
- to be supported / provided / enforced by this plugin by default
- similar to the
prhttps://github.com/scala-native/scala-native/pull/1194
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No source file, test, or entry point is named in the issue. Start by reviewing the referenced Scala.js and Scala Native issues and Scala Native PR 1194 to understand the naming problem and proposed policy. Done should mean the plugin has a clearly defined default policy for consistent project names.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100