base on A little beautifier tool for xcodebuild # xcbeautify [![](https://img.shields.io/endpoint?url=https%3A%2F%2Fswiftpackageindex.com%2Fapi%2Fpackages%2Fcpisciotta%2Fxcbeautify%2Fbadge%3Ftype%3Dswift-versions)](https://swiftpackageindex.com/cpisciotta/xcbeautify) [![CI](https://github.com/cpisciotta/xcbeautify/actions/workflows/ci.yml/badge.svg)](https://github.com/cpisciotta/xcbeautify/actions/workflows/ci.yml) [![Latest Release](https://img.shields.io/github/release/cpisciotta/xcbeautify.svg)](https://github.com/cpisciotta/xcbeautify/releases/latest) [![License](https://img.shields.io/github/license/cpisciotta/xcbeautify.svg)](LICENSE.md) ![Example Screenshot](.readme-images/example.png) **`xcbeautify` is a little beautifier tool for `xcodebuild`.** A faster alternative to `xcpretty` written in Swift. ## Features - [x] Human-friendly and colored output. - [x] Supports the new build system's output. - [x] Supports Xcode's parallel testing output. - [x] Supports formatting Swift Package Manager output. - [x] Supports generating JUnit reports. - [x] Supports macOS & Linux. - [x] Written in Swift: `xcbeautify` compiles to a static binary which you can bring anywhere. This also means less Ruby-dependant in your development environment and CI. ## Installation ### Homebrew ```bash brew install xcbeautify ``` ### [Mint](https://github.com/yonaskolb/mint) ```bash mint install cpisciotta/xcbeautify ``` ### Build from source ```bash git clone https://github.com/cpisciotta/xcbeautify.git cd xcbeautify make install ``` ## Usage ```bash xcodebuild [flags] | xcbeautify ``` If you want `xcbeautify` to exit with the same status code as `xcodebuild` (e.g. on a CI): ```bash set -o pipefail && xcodebuild [flags] | xcbeautify ``` For parallel and concurrent destination testing, it helps to use unbuffered I/O for _stdout_ and to redirect _stderr_ to _stdout_. ```bash NSUnbufferedIO=YES xcodebuild [flags] 2>&1 | xcbeautify ``` ```bash swift test [flags] 2>&1 | xcbeautify ``` ### GitHub Actions | ![GitHub Actions Summary](.readme-images/gh-summary.png) | |:--:| | *GitHub Actions Summary* | | ![GitHub Actions Comment](.readme-images/gh-comment.png) | |:--:| | *GitHub Actions Comment* | `xcbeautify` features an integrated GitHub Actions renderer that harnesses [workflow commands](https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions) to highlight warnings, errors, and results directly within the GitHub user interface. To utilize this function, simply run `xcbeautify` and add the `--renderer github-actions` flag during execution: ``` set -o pipefail && xcodebuild [flags] | xcbeautify --renderer github-actions ``` ### TeamCity `xcbeautify` features an integrated TeamCity renderer that harnesses [service messages](https://www.jetbrains.com/help/teamcity/service-messages.html) to highlight warnings, errors, and results directly within the TeamCity user interface. To utilize this function, simply run `xcbeautify` and add the `--renderer teamcity` flag during execution: ``` set -o pipefail && xcodebuild [flags] | xcbeautify --renderer teamcity ``` ### Azure DevOps Pipeline `xcbeautify` features an integrated Azure DevOps Pipeline renderer that harnesses [logging commands](https://learn.microsoft.com/en-us/azure/devops/pipelines/scripts/logging-commands) to highlight warnings, errors and results directly within the Azure DevOps Pipeline user interface. To utilize this function, simply run `xcbeautify` and add the `--renderer azure-devops-pipelines` flag during execution: ``` set -o pipefail && xcodebuild [flags] | xcbeautify --renderer azure-devops-pipelines ``` ## Development Generate Xcode project: ```sh make xcode ``` Release a new version, e.g. `x.y.z`: ```bash make release version=x.y.z ``` ## Contributing Please send a PR! ", Assign "at most 3 tags" to the expected json: {"id":"11380","tags":[]} "only from the tags list I provide: [{"id":77,"name":"3d"},{"id":89,"name":"agent"},{"id":17,"name":"ai"},{"id":54,"name":"algorithm"},{"id":24,"name":"api"},{"id":44,"name":"authentication"},{"id":3,"name":"aws"},{"id":27,"name":"backend"},{"id":60,"name":"benchmark"},{"id":72,"name":"best-practices"},{"id":39,"name":"bitcoin"},{"id":37,"name":"blockchain"},{"id":1,"name":"blog"},{"id":45,"name":"bundler"},{"id":58,"name":"cache"},{"id":21,"name":"chat"},{"id":49,"name":"cicd"},{"id":4,"name":"cli"},{"id":64,"name":"cloud-native"},{"id":48,"name":"cms"},{"id":61,"name":"compiler"},{"id":68,"name":"containerization"},{"id":92,"name":"crm"},{"id":34,"name":"data"},{"id":47,"name":"database"},{"id":8,"name":"declarative-gui "},{"id":9,"name":"deploy-tool"},{"id":53,"name":"desktop-app"},{"id":6,"name":"dev-exp-lib"},{"id":59,"name":"dev-tool"},{"id":13,"name":"ecommerce"},{"id":26,"name":"editor"},{"id":66,"name":"emulator"},{"id":62,"name":"filesystem"},{"id":80,"name":"finance"},{"id":15,"name":"firmware"},{"id":73,"name":"for-fun"},{"id":2,"name":"framework"},{"id":11,"name":"frontend"},{"id":22,"name":"game"},{"id":81,"name":"game-engine "},{"id":23,"name":"graphql"},{"id":84,"name":"gui"},{"id":91,"name":"http"},{"id":5,"name":"http-client"},{"id":51,"name":"iac"},{"id":30,"name":"ide"},{"id":78,"name":"iot"},{"id":40,"name":"json"},{"id":83,"name":"julian"},{"id":38,"name":"k8s"},{"id":31,"name":"language"},{"id":10,"name":"learning-resource"},{"id":33,"name":"lib"},{"id":41,"name":"linter"},{"id":28,"name":"lms"},{"id":16,"name":"logging"},{"id":76,"name":"low-code"},{"id":90,"name":"message-queue"},{"id":42,"name":"mobile-app"},{"id":18,"name":"monitoring"},{"id":36,"name":"networking"},{"id":7,"name":"node-version"},{"id":55,"name":"nosql"},{"id":57,"name":"observability"},{"id":46,"name":"orm"},{"id":52,"name":"os"},{"id":14,"name":"parser"},{"id":74,"name":"react"},{"id":82,"name":"real-time"},{"id":56,"name":"robot"},{"id":65,"name":"runtime"},{"id":32,"name":"sdk"},{"id":71,"name":"search"},{"id":63,"name":"secrets"},{"id":25,"name":"security"},{"id":85,"name":"server"},{"id":86,"name":"serverless"},{"id":70,"name":"storage"},{"id":75,"name":"system-design"},{"id":79,"name":"terminal"},{"id":29,"name":"testing"},{"id":12,"name":"ui"},{"id":50,"name":"ux"},{"id":88,"name":"video"},{"id":20,"name":"web-app"},{"id":35,"name":"web-server"},{"id":43,"name":"webassembly"},{"id":69,"name":"workflow"},{"id":87,"name":"yaml"}]" returns me the "expected json"