Skip to content

Latest commit

 

History

History
69 lines (64 loc) · 3.04 KB

DEVELOPMENT.md

File metadata and controls

69 lines (64 loc) · 3.04 KB
Raw

Development

  • Make sure to use the latest lts of node via nvm use --lts or set it to default via nvm alias default lts/* (adjust version from nvm ls)
  • VSCode should automatically run npm run watch while developing
  • Run tests manually: npm run test

Publishing

  • Make sure to update the version in package.json, and optionally tag the commit like git tag "<version>" and git push origin "<version>"
  • Make sure to update CHANGELOG.md
  • Tests will run before publishing to VSCode marketplace via vscode:prepublish in package.json
  • If personal access token as expired, run vsce login <username>
    • Store latest access key in AWS, retrieve via: aws secretsmanager get-secret-value --secret-id vsce-publish-token
  • To publish run vsce publish
  • Update vsce with npm install -g vsce

Feature Todo List

  • Syntax highlighting (calc file type?)
  • $
  • %
  • auto detect some date formats
  • Settings
  • tps as a unit
  • sum above lines until last empty line
  • implement/extend round()/floor()/ceil() to work with dates
  • more stuff from numi: https://github.com/nikolaeu/numi/wiki/Documentation
  • this could actually benefit from tests...
  • Copy to clipboard command (just text? text but insert =? html? html table?)
  • Sort by output (should work within header sections? within empty line border?)
  • upgrade mathjs version to latest, but have unit tests first - gets binary support
  • base (binary, hex) conversion
  • "time"
  • time in <city>
  • "next friday"
  • support for "ago"
  • Seems to be a bug if a document has 1 USD in it, when it loads, it caches a wrong result before currencies load?
  • convert hex to rgb and vice versa?
  • use oC and oF as "degrees c" and "degress f"
  • px/points units
  • formatter needs to take settings object for performance and tests
  • more efficient use of scopes for the reassignUnitError
  • output should be an error when reassigning a unit
  • ability to change px per inch and px per em
  • finish an actual readme
  • don't count headers for longest line
  • Local currency conversion in output
  • enable "in $"
  • enable mph and kph
  • syntax highlighting for mistakenly assigning ANY keyword (new. math.js native constants units and functions)
  • decoration explanation to accompany syntax highlighting for reassigning builtins
  • Enable "yesterday 11pm"
  • Decide on better file extension
  • Fix math API TODO what was this for...?
  • Allow things like $4 + 4 (works for other units but not currency)
  • Enable more comment types similar to //qalc:on to fit other language styles
    • HTML format
    • Markdown ```qalc format
    • etc
  • Enable processing calculations within the comments of other languages (e.g. within Javadoc)