Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
WorkingClass is an human readable syntax to write tasklists. Besides being easy to read it's fully parseable, so you can work with the tasks in Ruby.
Add this line to your application's Gemfile:
gem 'working_class'
And then execute:
$ bundle
Or install it yourself as:
$ gem install working_class
Keep in mind that all dates are formatted like this: DD.MM.YYYY
or D.M.YY
Tasklist Name
---
[ ] My first task
[X] A finished task
[ ]{1.1.15} A task with a due date
[ ]{1.1.15}(31.1.15 12:00) A task with a date and a reminder
[ ]{1.1.15}(-1 12:00) A task with a date and a »relative« reminder
[ ]{1.1.15}(12:00) A task that will remind me at 12:00 1.1.15
You see it's pretty easy to write tasks like this.
At the moment the order of date and reminder is mandatory.
So you can't write:
My Tasklist
---
[ ](REMINDER){DATE} My Task
A tasklist name is written like this:
The ---
is important, don't forget it.
Every tasklist should have a name.
Tasklist Name
---
…
Both tasks are equal, they are both not finished.
We recommend the [ ]
, it looks much nicer.
Shopping List
---
[ ] Jeans
[] T-Shirts
Groceries List
---
[X] Milk
[x] Bread
To write a finished task you have to write a [X]
or [x]
. It's not important
whether you write a small x or a capital X, both characters are recognized as
a finished task.
It doesn't matter if you write your dates DD.MM.YY or D.M.YY or DD.MM.YYYY WorkingClass accepts all of those formats, as long as it is a valid date.
The Party List
---
[X]{6.2.2015} Birthday Party
[X]{13.2.15} Another Birthday Party
Every task can have a reminder. You have several options when adding a reminder.
All times are 24h.
You can write a full date without a time and the parser will add the default time (9:00) automatically.
An even more awesome Party List
---
[ ](31.1.15) This time of year
If you already specified a date for the task you can use a relative reminder
by writing -2
, this specifies that you want to be reminded 2 days earlier.
The parser will add the default time, if you didn't add one.
The after party
---
[ ]{2.1.15}(-2) You will have to clean up everthing.
Important: This only works if your task has already a date.
This will not work:
The after party
---
[ ](-2) You will have to clean up everthing.
So enough of that, what about the times. You can easily add a time to your reminder
My Finals
---
[ ]{26.1.15}(15:00) English
If you don't specify a relative or absolute date you will be reminded at 15:00 on the same day.
You can also combine absolute or relative dates with a time
My Finals
---
[ ]{26.1.15}(24.1.15 9:00) Don't panic.
[ ]{26.1.15}(-1 15:00) English
Check out the full documentation
require 'working_class'
string = """
My Finals
---
[ ]{26.1.15}(15:00) English
"""
WorkingClass.load(string) # => WorkingClass::Tasklist
# or if you have a file
WorkingClass.load_file('./examples/example_1.txt') # => WorkingClass::Tasklist
git checkout -b my-new-feature
)git commit -am 'Add some feature'
)git push origin my-new-feature
)FAQs
Unknown package
We found that working_class demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.