Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation issue: actions.write with args content #13124

Open
GMNGeoffrey opened this issue Feb 27, 2021 · 1 comment
Open

Documentation issue: actions.write with args content #13124

GMNGeoffrey opened this issue Feb 27, 2021 · 1 comment
Labels
P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Documentation Documentation improvements that cannot be directly linked to other team labels team-Rules-API API for writing rules/aspects: providers, runfiles, actions, artifacts type: documentation (cleanup)

Comments

@GMNGeoffrey
Copy link
Contributor

Documentation URL: https://docs.bazel.build/versions/master/skylark/lib/actions.html#write

"May be a either a string or an actions.args() object." is all it says about passing an args object to content here. What does that actually do though? How are the args processed? What is the intended use case?

@brandjon
Copy link
Member

brandjon commented Mar 4, 2021

The wording could be clarified to indicate that the args is processed as usual and the resulting string becomes the file contents (as opposed to the arguments of some command line).

@brandjon brandjon added P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) type: documentation (cleanup) and removed untriaged labels Mar 4, 2021
@brandjon brandjon added untriaged team-Rules-API API for writing rules/aspects: providers, runfiles, actions, artifacts and removed team-Build-Language labels Nov 4, 2022
@ShreeM01 ShreeM01 added the team-Documentation Documentation improvements that cannot be directly linked to other team labels label Jan 10, 2023
@comius comius added P3 We're not considering working on this, but happy to review a PR. (No assignee) and removed P4 This is either out of scope or we don't have bandwidth to review a PR. (No assignee) untriaged labels Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 We're not considering working on this, but happy to review a PR. (No assignee) team-Documentation Documentation improvements that cannot be directly linked to other team labels team-Rules-API API for writing rules/aspects: providers, runfiles, actions, artifacts type: documentation (cleanup)
Projects
None yet
Development

No branches or pull requests

5 participants