foretaginc / engineering

Foretag's Development toolkit: config files, linting, tooling and IDE extensions

Engineering at Foretag

🪧 This repository contains multiple packages that form our engineering toolchain built for internal and public use as part of our Engineering focus.

World-class projects need first-class developer experience. We work with our engineers and outside contributors to create tooling - that is optimal for a seamless experience across our toolchain. Developed from the ground up to reduce boilerplate and increase consistency to help keep your head in the game.

Our ethos inspires transparency and innovation, and our engineering guide is no exception. Here you can find all the resources: guides, IDE extensions, shareable configs, and wikis to help you work across any of our projects.

Why?

We strive for a consistent, easy-to-use environment for all our engineers and contributors to minimize friction, scale faster and improve the quality of our projects. If you have ideas to improve this experience, open an issue and write away - we're all ears.

Links

• Foretag Engineering
• Technology Stack
• Github Community files

Repository

For your convenience, this repository is available publicly on Radicle and Github: it hosts packages disturbed across NPM, crates.io, and other package managers.

Packages

• Engineering Guide
• Development Toolkit for VSCode
• Frontend Toolkit for VSCode
• Rust Toolkit for VSCode
• Bun Toolkit for VSCode

engineering's Issues

Sharable EditorConfig

Currently, an .editorconfig file has to be created per project, this is not scalable as changes to this would have to be made on every project, instead we need to follow a preset convention via a shareable config, this has been discussed on: editorconfig/editorconfig#236 and currently blocked.