Thought on version control strategy
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 15
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
About the fe version
fe is designed to separate the build environment of differents Font-End tech stacks (like: React / Rxjs / Angular2 / Vue2 ...) from project dependency and manage workflow to improve develop experience.
There is only one bridge section fe.config.json between fe and project, to replace quikly switch different fe version, keep fe.config.json flexable and extendable, fe should cover each of projects, some default configure can be automatic written and other different configs show on doc and changelog.
Thinking about the differents between two project 0.1.0 and 0.2.0:
-
fe.config.json -
other custom configs(webpack / babel)
-
boilerplate
-
component
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
Start with fe.config.json and the listed webpack and Babel configurations, boilerplate, and components; compare how the 0.1.0 and 0.2.0 versions differ. Done requires a concrete version-control strategy covering those differences, with the affected entry points or documentation identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- babel, javascript, webpack
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100