A fast, small (~0.5 KB gzipped) and dependency-free JavaScript library to sort arrays. It uses quick sort internally to sort arrays _in place_, without recursion. Simply replace JavaScript's built-in `Array.prototype.sort` with f-sort's `sort` to see ~2x
Lists the contents of directories in a tree-like format, similar to the Linux tree command.
Sort an Object or package.json based on the well-known package.json keys
JSS plugin that ensures style properties extend each other instead of override
Run operations on a graph, maximizing parallelism
Easy autofixable import sorting
ESLint summary formatter aggregating results by rule
PostCSS plugin for sorting and combining CSS media queries with mobile first / **desktop first methodologies
Measure the churn/complexity score. Higher values mean hotspots where refactorings should happen.
Micro library for sorting arrays using the firstBy().thenBy().thenBy() syntax
vfile utility to sort messages by line/column
Sort the keys of an object
The custom `sort` method (mobile-first / desktop-first) of CSS media queries for `postcss-sort-media-queries`, `css-mqpacker` or `pleeease` (which uses css-mqpacker) or, perhaps, something else ))
Fork of eslint rule that sorts keys in objects (https://eslint.org/docs/rules/sort-keys) with autofix enabled
Sort an object's keys, including an optional key list
Sort array elements in ascending order.
Sort array elements in descending order.
Sort objecy keys by length
Sort YAML files alphabetically
Fast and powerful array sorting. Sort an array of objects by one or more properties. Any number of nested properties or custom comparison functions may be used.
ESLint rule for enforcing consistent ES6 class member order.
A prettier plugins to sort imports in provided RegEx order
Sort the keys in an object.
Sort interface and string enum keys
Sort GFF/GTF by chromosome + position
Sort a VCF by chromosome and position — Rust port of bcftools sort
You'll be able to use Array#bogosort (this is an alias for: Array#bogo_sort) And Array#bogosort! (this is an alias for: Array#bogo_sort!) But Array#bogo_sort can't sort Array include some Classes that can't compared At this time, Array#bogo_sort return nil
RawkLog - RAWK - Rail's Analyzer With Klass for log files
== Welcome to syc-spector home :: https://github.com/sugaryourcoffee/syc-spector == Description The sycspector scans a file for patterns provided on the command line. Lines that match the pattern are saved to a file with valid values and those lines that don't match the pattern are added to a file with invalid values. The valid and invalid files as well as the used pattern are stored in a history file. The saved values are used for a subsequent call to sycspector with --show and -f for fix to show the results or to prompt the invalid values to fix them. Fixed values can be appended to the valid values file. == Installation sycspector can be installed as a gem from http://RubyGems.org with $ gem install syc-spector == Invokation Examples Rearches for email addresses in the provided file 'email_addresses' $ sycspector email_addresses -p email Lines that are not recognized can be prompted, fixed and appended to the valid file with $ sycspector -fa To show the result of the invokation use $ sycspector --show To fix the values from the input file at the first scan $ sycspector -f email-addresses -p email To sort the values $ sycspector -s email-addresses -p email To fix, sort and remove duplicates (individualize) $ sycspector -fsi email-addresses -p email Matching patterns like 'name, firstname' $ syscpector name -p "\w+, \w+" Scanning only whole lines use $ sycspector name -p "\A\w+, \w+\A" If the file contains lines like "Doe, John and Doe, Jane" these won't be saved at the first scan but can be scanned with the --fix switch and appended to the valid values from the last run $ sycspector -fa Fixing a specific file by specifying the invalid file as inputfile $ sycspector -fa 2013016-083346_invalid_name -o 2013016-083346_valid_name Specifying the file where the results (valid and invalid) should go to $ sycspector -fa -o outputfile To process all at once $ sycspector -fis inputfile -o outputfile -p "\A\w+, w+\Z" --show == License syc-spector is released under the {MIT License}[http://www.opensource.org/licenses/MIT].
:title: The Ruby API :section: PYAPNS::Client There's python in my ruby! This is a class used to send notifications, provision applications and retrieve feedback using the Apple Push Notification Service. PYAPNS is a multi-application APS provider, meaning it is possible to send notifications to any number of different applications from the same application and same server. It is also possible to scale the client to any number of processes and servers, simply balanced behind a simple web proxy. It may seem like overkill for such a bare interface - after all, the APS service is rather simplistic. However, PYAPNS takes no shortcuts when it comes to completeness/compliance with the APNS protocol and allows the user many optimization and scaling vectors not possible with other libraries. No bandwidth is wasted, connections are persistent and the server is asynchronous therefore notifications are delivered immediately. PYAPNS takes after the design of 3rd party push notification service that charge a fee each time you push a notification, and charge extra for so-called 'premium' service which supposedly gives you quicker access to the APS servers. However, PYAPNS is free, as in beer and offers more scaling opportunities without the financial draw. :section: Provisioning To add your app to the PYAPNS server, it must be `provisioned` at least once. Normally this is done once upon the start-up of your application, be it a web service, desktop application or whatever... It must be done at least once to the server you're connecting to. Multiple instances of PYAPNS will have to have their applications provisioned individually. To provision an application manually use the `PYAPNS::Client#provision` method. require 'pyapns' client = PYAPNS::Client.configure client.provision :app_id => 'cf', :cert => '/home/ss/cert.pem', :env => 'sandbox', :timeout => 15 This basically says "add an app reference named 'cf' to the server and start a connection using the certification, and if it can't within 15 seconds, raise a `PYAPNS::TimeoutException` That's all it takes to get started. Of course, this can be done automatically by using PYAPNS::ClientConfiguration middleware. `PYAPNS::Client` is a singleton class that is configured using the class method `PYAPNS::Client#configure`. It is sensibly configured by default, but can be customized by specifying a hash See the docs on `PYAPNS::ClientConfiguration` for a list of available configuration parameters (some of these are important, and you can specify initial applications) to be configured by default. :section: Sending Notifications Once your client is configured, and application provisioned (again, these should be taken care of before you write notification code) you can begin sending notifications to users. If you're wondering how to acquire a notification token, you've come to the wrong place... I recommend using google. However, if you want to send hundreds of millions of notifications to users, here's how it's done, one at a time... The `PYAPNS::Client#notify` is a sort of polymorphic method which can notify any number of devices at a time. It's basic form is as follows: client.notify 'cf', 'long ass app token', {:aps=> {:alert => 'hello?'}} However, as stated before, it is sort of polymorphic: client.notify 'cf', ['token', 'token2', 'token3'], [alert, alert2, alert3] client.notify :app_id => 'cf', :tokens => 'mah token', :notifications => alertHash client.notify 'cf', 'token', PYAPNS::Notification('hello tits!') As you can see, the method accepts paralell arrays of tokens and notifications meaning any number of notifications can be sent at once. Hashes will be automatically converted to `PYAPNS::Notification` objects so they can be optimized for the wire (nil values removed, etc...), and you can pass `PYAPNS::Notification` objects directly if you wish. :section: Retrieving Feedback The APS service offers a feedback functionality that allows application servers to retrieve a list of device tokens it deems to be no longer in use, and the time it thinks they stopped being useful (the user uninstalled your app, better luck next time...) Sounds pretty straight forward, and it is. Apple recommends you do this at least once an hour. PYAPNS will return a list of 2-element lists with the date and the token: feedbacks = client.feedback 'cf' :section: Asynchronous Calls PYAPNS::Client will, by default, perform no funny stuff and operate entirely within the calling thread. This means that certain applications may hang when, say, sending a notification, if only for a fraction of a second. Obviously not a desirable trait, all `provision`, `feedback` and `notify` methods also take a block, which indicates to the method you want to call PYAPNS asynchronously, and it will be done so handily in another thread, calling back your block with a single argument when finished. Note that `notify` and `provision` return absolutely nothing (nil, for you rub--wait you are ruby developers!). It is probably wise to always use this form of operation so your calling thread is never blocked (especially important in UI-driven apps and asynchronous servers) Just pass a block to provision/notify/feedback like so: PYAPNS::Client.instance.feedback do |feedbacks| feedbacks.each { |f| trim_token f } end :section: PYAPNS::ClientConfiguration A middleware class to make `PYAPNS::Client` easy to use in web contexts Automates configuration of the client in Rack environments using a simple confiuration middleware. To use `PYAPNS::Client` in Rack environments with the least code possible `use PYAPNS::ClientConfiguration` (no, really, in some cases, that's all you need!) middleware with an optional hash specifying the client variables. Options are as follows: use PYAPNS::ClientConfiguration( :host => 'http://localhost/' :port => 7077, :initial => [{ :app_id => 'myapp', :cert => '/home/myuser/apps/myapp/cert.pem', :env => 'sandbox', :timeout => 15 }]) Where the configuration variables are defined: :host String the host where the server can be found :port Number the port to which the client should connect :initial Array OPTIONAL - an array of INITIAL hashes INITIAL HASHES: :app_id String the id used to send messages with this certification can be a totally arbitrary value :cert String a path to the certification or the certification file as a string :env String the environment to connect to apple with, always either 'sandbox' or 'production' :timoeut Number The timeout for the server to use when connecting to the apple servers :section: PYAPNS::Notification An APNS Notification You can construct notification objects ahead of time by using this class. However unnecessary, it allows you to programmatically generate a Notification like so: note = PYAPNS::Notification.new 'alert text', 9, 'flynn.caf', {:extra => 'guid'} -- or -- note = PYAPNS::Notification.new 'alert text' These can be passed to `PYAPNS::Client#notify` the same as hashes
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.