mirror of
https://github.com/bitburner-official/bitburner-src.git
synced 2026-04-16 06:18:42 +02:00
dcd2f33f7c
* Update api-documentor and api-extractor. #1566 follow-up.
I have verified that the HTML/markdown table generation bug in
[#4878](https://github.com/microsoft/rushstack/issues/4878) in rushstack
for api-documentor has been fixed as per rushstack#5256. The testcase
[repro](https://github.com/catloversg/api-documenter-bug-pr-4578) now
produces the correct expected output.
I have confirmed that the generated output in bitburner from
`npm run doc` now generated HTML tables, and correctly inserts
a blank line between the </table> and the follow line (e.g. Returns).
Stylisticly it could use some whitespace, but it is correctly rendered.
This commit is only the updated packages, not the updated generated
documentation. I assume that is automatically generated by the GitHub
workflow.
* Follow up to 5f732a6f35, include `npm run doc` changed docs.
* Add missing license info
* Fix React warning
---------
Co-authored-by: CatLover <152669316+catloversg@users.noreply.github.com>
1.2 KiB
1.2 KiB
Home > bitburner > Stanek > canPlaceFragment
Stanek.canPlaceFragment() method
Check if fragment can be placed at specified location.
Signature:
canPlaceFragment(rootX: number, rootY: number, rotation: number, fragmentId: number): boolean;
Parameters
|
Parameter |
Type |
Description |
|---|---|---|
|
rootX |
number |
Root X against which to align the top left of the fragment. |
|
rootY |
number |
Root Y against which to align the top left of the fragment. |
|
rotation |
number |
A number from 0 to 3, the amount of 90-degree turns to take. |
|
fragmentId |
number |
ID of the fragment to place. |
Returns:
boolean
true if the fragment can be placed at that position. false otherwise.
Remarks
RAM cost: 0.5 GB