Method needed to get rake command line options for spawning new rake job
还没有人认领这个 Issue。
评估
调研方向
从 Rake.application 开始，跟踪 handle_options 和 standard_rake_options 入口点，以了解命令行选项是如何被解析和保留的。检查顶层 Rakefile 在子目录中生成作业时如何读取已解析的值。完成的标准是：已解析的选项可通过公开的 application 属性获取，而无需调用方重复解析选项。
由索引模型根据 Issue 内容生成。
描述
I am implementing a "top level" Rakefile that will spawn off rake jobs in sub-directories.
This is not hard to do, except that I want to pass the same options to the jobs that was passed to the original rake command. I cannot find a way to reliably find out what those options were without using some quasi private methods such as handle_options in the application object. I do not want the targets, just the options.
Could we add code to handle_options to put the options that are parsed into an array that is a public attribute of the application object?
Then I could grab the rake options by a simple use of something like:
Rake.application.rake_options
If there is some way to easily do this that I am missing please let me know. I originally was just iterating over the ARGV entries and grabbing things out of it, but quickly realized that the command line options may or may not have an argument following a "-" prefixed option and there is no way I can know that without duplicating all the code in standard_rake_options.
Thanks.
- 主要语言
- Ruby
- 星标
- 2.5k
- 派生
- 650
- 平均合并
- 6 分钟
- 30 天内合并 PR
- 3
贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
ruby/rake 的其他 Issue
-
难度 3/5 1-2 天 新手友好度 68/100
-
难度 3/5 1-2 天 新手友好度 48/100
-
难度 5/5 一周以上 新手友好度 28/100
-
难度 1/5 1 小时以内 新手友好度 45/100
-
难度 4/5 3-5 天 新手友好度 38/100
相似的 Issue
-
SyncEm always forwards a dummy block, so wrapped methods lose their no-block/Enumerator behavior 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
-
bug
难度 2/5 1-3 小时 新手友好度 75/100
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
endoflife-date/endoflife.date#11086 ·
-
internal
难度 1/5 1 小时以内 新手友好度 88/100
Kong/developer.konghq.com#7322 ·
-
bug P2
难度 2/5 1-3 小时 新手友好度 88/100