Quickly add .devcontainer configuration to any JavaScript project, and more!
INTERNAL ZETRO DEVELOPEMNT COMPILER
Quickly add .devcontainer configuration to any JavaScript project, and more!
Interface to Abap Developer Tools webservice
A simple table with sort and filteer functions
Made with create-react-library
Command line utilities for node development.
ADASH Services
Interface to Abap Developer Tools webservice
abapGit serialization plugin for adt-cli — round-trips ADT objects to/from the abapGit on-disk format
gCTS (git-enabled CTS) plugin for adt-cli — repository, commit, pull/push operations on SAP gCTS
CAP plugin for integration with SAP ABAP ADT (ABAP Development Tools)
Unofficial PostNL SDK for Node.js inspired by Resend
Patched fork of abap-adt-api with sap-client/sap-language, lock URL fix, and Content-Type fix
基于 abap-adt-api 的修改版
As this now supports pluggable HTTP clients, we can call the API over RFC as eclipse does.
CLI for generating devcontainers
typescript client for the postnl ecommerce api (v4-first, legacy supported)
Device Connector CLI
Device Connector relay server
Core crate for the Device Connector
Device Connector Daemon
Rust Core Project
This is the DevCenter client library for developing .NET applications with rich experience.
generated REST API bindings
Microsoft Azure Resource Manager client SDK for Azure resource provider Microsoft.DevCenter.
generated REST API bindings
CLI tool for building and packaging devcade games
Types used by the devcade onboard socket
Devcade input support library for Bevy+Rust!
DevCycle Ruby Server SDK, for interacting with feature flags created with the DevCycle platform.
Parser for Heroku Dev Center's content
CLI to interact with Heroku's Dev Center
The DevCreek gem enables programmers to collect and transmit metrics from their Ruby Test::Unit and RSpec test suites to a DevCreek server. Please visit the DevCreek site (http://devcreek.com/index.html) for more info. == FEATURES/PROBLEMS: Supported frameworks include Test::Unit and RSpec (> 1.10). == SYNOPSIS: The DevCreek Ruby Gem is library that, when loaded, will automatically listen to and collect metrics from your Test::Unit/RSpec unit tests. All you have to do is load the DevCreek library in your code and give it your DevCreek account info so that it can transmit the metrics to the server. Here is the simplest example of how to load DevCreek: -------- #Load the devcreek gem require 'rubygems' require 'devcreek' #set your account info DevCreek::Core.instance().load_from_yaml("#{ENV['HOME']}/.yoursettingsfile.devcreek.yml") -------- There are two ways to provide DevCreek with your account settings. The first (as shown above) is to point DevCreek to a settings file. The 'enabled' attribute tells devcreek whether or not it should actually transmit the metrics that it collects. The yaml file would like this: -------- user: your_devcreek_username password: your_devcreek_password project: your_devcreek_project enabled: true -------- The other way to provide DevCreek with your settings is via a hash. So, instead of loading a yaml file, you could do this: -------- #Load the devcreek gem require 'rubygems' require 'devcreek' #set your account info DevCreek::Core.instance().load( :user => 'your_devcreek_username', :password => 'your_devcreek_password', :project => 'your_devcreek_project', :enabled => true ) -------- The first method is preferrable because it allows you to keep your account settings outside of your project (and therefore your source control tool). If you only have 1 test file, you can place the code to load devcreek in the test file and your done. However, most projects will have many test files. In this case, you need to make sure that the Ruby interpreter loads devcreek before running the test classes. This can be done via the Ruby '-r' option. For example, assuming your code to load devcreek is in a file called foo.rb, you would run your tests from the command line like this: ruby -r foo.rb test/test_* If you run your tests from a Rakefile, then you need to tell rake to include the -r option when it runs the tests (rake runs it's tests in a separate Ruby process). You can do this pretty easily in your Rakefile, like so; -------- require 'rake/testtask' Rake::TestTask.new('all_tests') do |t| t.ruby_opts = ['-r foo.rb'] t.test_files = ['test/test_*.rb'] end --------
Simple development flow helper that disables development.log, adds STDOUT logging instead, loads .env
Provides generated HTML data for Rails applications.
Description text.
Create development SSL/TLS certificates without a hassle
DevCycle Ruby Server SDK, for interacting with feature flags created with the DevCycle platform.
Write a longer description or delete this line.
Provides generated HTML data for Rails applications.
Provides generated HTML data for Rails applications.
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.
No description provided.