Git Product home page Git Product logo

docs_gm's People

Contributors

gitter-badger avatar greenkeeper[bot] avatar jhm-ciberman avatar phgn0 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

Forkers

gitter-badger

docs_gm's Issues

An in-range update of yargs is breaking the build 🚨

The dependency yargs was updated from 13.2.2 to 13.2.4.

🚨 View failing branch.

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.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

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

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Document template.json file

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.

An in-range update of @types/xml2js is breaking the build 🚨

The devDependency @types/xml2js was updated from 0.4.3 to 0.4.4.

🚨 View failing branch.

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.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of nunjucks is breaking the build 🚨

The dependency nunjucks was updated from 3.1.3 to 3.1.4.

🚨 View failing branch.

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.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

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

FAQ and help

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)

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)

GMS2.3 compatibility

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

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]

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from 10.11.0 to 10.11.1.

🚨 View failing branch.

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.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

FAQ and help

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 RuleFunctionSignatureInDescription

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.

Feature Request: folder scoped docs

Based on my gamemaker usage I have some improvements in mind:

  • generate documentation for all scripts in a (gamemaker) folder on a single page,
    with links to subfolders
  • ability to set a description / usage text for each folder

I could implement it, but I wanted your opinion :)

btw I really like the work you did here :)

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

  • Added the new Node.js version to your .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.

More information on this issue

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 🤖


FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

docs_gm should combine duplicate arguments definitions

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.

    • If true, the arguments with the same name will be merged.
    • If false, it will be added as different arguments.
  • Create a validation rule RuleDuplicateParam that detects parameters with duplicated names.

    • If active, and there are duplicate arguments with the same name, it should warn on the console or ignore the script acording to the rule configuration.

Variable project root

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.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.