jhm-ciberman / docs_gm Goto Github PK
View Code? Open in Web Editor NEWThe fantastic documentation generator for GameMaker:Studio and GameMaker Studio 2
Home Page: https://jhm-ciberman.github.io/docs_gm
License: MIT License
The fantastic documentation generator for GameMaker:Studio and GameMaker Studio 2
Home Page: https://jhm-ciberman.github.io/docs_gm
License: MIT License
13.2.2
to 13.2.4
.This version is covered by your current version range and after updating it in your project the build failed.
yargs is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 14 commits.
a6e67f1
chore(release): 13.2.4
fc13476
chore: update standard-verison dependency
bf46813
fix(i18n): rename unclear 'implication failed' to 'missing dependent arguments' (#1317)
a3a5d05
docs: fix a broken link to MS Terminology Search (#1341)
b4f8018
build: add .versionrc that hides test/build
0c39183
chore(release): 13.2.3
08e0746
chore: update deps (#1340)
843e939
docs: make --no-
boolean prefix easier to find in the docs (#1338)
84cac07
docs: restore removed changelog of v13.2.0 (#1337)
b20db65
fix(deps): upgrade cliui for compatibility with latest chalk. (#1330)
c294d1b
test: accept differently formatted output (#1327)
ac3f10c
chore: move .hbs templates into .js to facilitate webpacking (#1320)
0295132
fix: address issues with dutch translation (#1316)
9f2468e
doc: clarify parserConfiguration object structure (#1309)
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
There is no official documentation for the template.json file.
The objective is to create an MD file with the documentation for all the properties for template.json.
0.4.3
to 0.4.4
.This version is covered by your current version range and after updating it in your project the build failed.
@types/xml2js is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Add RuleNoParamType and RuleNoParamDescription to detect when a param has no Type declaration or no description
it shouldn't be copied.
TODO:
3.1.3
to 3.1.4
.This version is covered by your current version range and after updating it in your project the build failed.
nunjucks is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
The new version differs by 7 commits.
11262e5
Release v3.1.4
bcd45fc
Merge pull request #1165 from stigkj/master
40480f0
Fix engine version for Node v11.1.0
3512ca6
Merge pull request #1161 from jonathanchu/master
9dc07dc
Fix dependency version for node v11.0.0
39bb716
Merge pull request #1126 from TheDancingCode/issue-126
4d4dc40
Escape unicode newlines when compiling
See the full diff
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Folders with only private scripts are still added in the documentation (but no script is shown)
For example, consider the following:
+ scripts
+ my_folder
- my_public_script
- another public script
+ my_other_folder
- _my_private_script
- _my_other_private_script
If you generate the documentation with docs_gm generate
the folder my_other_folder
will be still shown on the documentation page. But no script will be inside the folder since all scripts are private.
The expected behavior should be that the empty folders are removed from the documentation (before rendering the documentation)
Add RuleNoReturns to detect when a script has a return but no documentation for it.
Also, RuleNoReturnsType to detect when a return documentation has no type defined.
Validate docs_gm.json and template.json using JSON Schema
Sorry for posting under issues, wanted to know if this project will support GMS2.3 or if it was abandoned?
Add verbosity level debug option. Example:
docs_gm generate -vvvv
Should be more verbose and print debug messages like:
Rendering page for element: tweenline2 [folder]
10.11.0
to 10.11.1
.This version is covered by your current version range and after updating it in your project the build failed.
@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
This rule should detect if the @description
tag has a function signature instaed of the actual function description.
This is because, when you import a GMS1 project into GMS2, the @description
tag is filled with the function generated signature.
Add DocScript.signature property that returns the full script(a,b,c) signature.
Example:
<b>{{ script.signature }}</b>
Should render to:
<b>my_script(para, foo, bar);</b>
Add docs_gm-basic as a subtree of docs_gm
Actually, docs_gm does not throw any error if the files are not parsed correctly.
It should throw an error.
Based on my gamemaker usage I have some improvements in mind:
I could implement it, but I wanted your opinion :)
btw I really like the work you did here :)
Markdown should be optional, acording to http://usejsdoc.org/plugins-markdown.html
It should be enabled by default, but you should be able to disable it using the docs_gm.json
file.
To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:
.travis.yml
If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.
Greenkeeper has checked the engines
key in any package.json
file, the .nvmrc
file, and the .travis.yml
file, if present.
engines
was only updated if it defined a single version, not a range..nvmrc
was updated to Node.js 10.travis.yml
was only changed if there was a root-level node_js
that didn’t already include Node.js 10, such as node
or lts/*
. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.For many simpler .travis.yml
configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
Consider the following documentation:
/// @description tween_to(target_object, duration, vars);
/// @function tween_to
/// @param target_object
/// @param duration
/// @param vars
/**
* Creates a new tween that animates the target_object variables to the specified
* destination values (from the current values) and returns its index.
*
*
* @param {Object | instance | array of objects or instances or mixed} target_object
* Target object whose properties should be affected. The target can be any game maker object.
* You can also pass an array of objects or instances.
*
* @param {real} duration
* Duration in seconds (or frames if "useframes" true is set in the vars parameter)
*
* @param {array} vars
* The special vars array.
*/
Actually, docs_gm recognizes 6 arguments: ["target_object", "duration", "vars", "target_object", "duration", "vars"]
Since they have the same name, the proposed solution can be:
Create an option "combineDuplicateParams"
in the ProjectConfig.
Create a validation rule RuleDuplicateParam
that detects parameters with duplicated names.
Actually, the project root is allways the scripts folder. It would be great if you can start your documentation from a subfolder.
For example, given:
+ scripts
+ inventory_system
- script1
- script2
- ...
the project root normally starts on the "scripts" folder, but it would be great to start on the "inventory_system" folder.
Add asset() helper to auto generate URLs to css/js/image files
Support inline @link tags
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.