sourcejs/Source

rename stuff like options.js and /assets/ to names more sourcejs related

Open

#229 建立於 2016年5月28日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)JavaScript (552 star) (49 fork)batch import
good first contributionhelp wanted

描述

Now that install by dependency is going to become the official way and the only way in 0.7.x I think we should think about being a bit less invasive upon people's environment.

Imagine if every npm dependency just asked to add a options.js to the root of the folder? I propose we rename it to something like sourcejs.config.js if that's possible.

Also I think all template-overrides, assets overrides and core-overrides could be in a sourcejs folder by default, instead of in the root. Another options would be to rename them to sourcejs-assets, sourcejs-templates.. etc.

貢獻者指南

技術棧
javascriptnodejs
領域
frontenddeveloper experiencetooling
議題類型
refactor
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
2
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
SourceJS project structurenpm package configurationJavaScript/Node.js basics
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
65
研究方向
Start by examining the current root directory for files like options.js and folders named assets, templates, core overrides. Identify all imports or references to these files and folders in the codebase, particularly in configuration files and module loading. Rename options.js to sourcejs.config.js and move overrides into a sourcejs/ subdirectory, updating all internal references. Check the repository's wiki or documentation for any mentions of these paths.