💪 Perl 6 completions and linting
Perl 6
Switch branches/tags
Nothing to show
Latest commit 4493744 Apr 26, 2017 @MadcapJake committed on GitHub Merge pull request #6 from samcv/SPDX-license
Use SPDX identifier in license field of META.info
Permalink
Failed to load latest commit information.
bin Finish `--all` support on the command line Jan 28, 2016
lib Add `--all` support to Diviner Jan 28, 2016
logotype Add logo for module site Jan 28, 2016
t Fix path in fixtures to match travis Jan 28, 2016
.gitignore
.travis.yml Add travis config Jan 28, 2016
LICENSE Add license Jan 19, 2016
META.info Use SPDX identifier in license field of META.info Apr 26, 2017
README.md Add slack badge Feb 1, 2016
pm6-info Add completions from meta-info `depends` array. Jan 27, 2016
workout-camelia.png Add readme and image Jan 19, 2016

README.md

Bring your Perl 6 workflow to the next level!


Coverage Status Build Status Issues License Slack

About | Usage | Documentation | Rules | Contributing


About

P6Dx provides a platform for leveraging language workflow tools in any text editor. The included p6dx bin script provides several flags with easy access to:

  • Code completions (per file, per package, even required packages)
  • Syntax checking (cascading rule declarations)
  • And more? (Code coverage? ctags? let me know!)

Usage

Install

panda install p6dx
zef install p6dx

Config

Mostly TBD. You will be able to specify syntax rules in either a user's home folder, the project's base path, a manually supplied file, or via a special comment syntax.

Command Line

p6dx # displays help
p6dx --complete="$part_of_string" --file=$file_or_dir # completions
p6dx --tags --json # prints json format of all tags
p6dx --tags --ctag # prints ctag representation
p6dx --examine=$file_or_dir # syntax check [NOT YET IMPLEMENTED]

Editors

Currently no editors are using P6Dx, however after I've finalized some of the data design, I plan to integrate this into linter-perl6 for Atom Editor and then I'll try my hand at writing a Gedit plugin.

Contributing

I'm gonna try and keep some high-level issues for each feature. Right now, I mostly need help hashing out conventions and solving bugs in my really early code. Feel free to submit PRs too though!

Ideas

  • code coverage
  • ctags generation
  • code formatter

Acknowledgements