This quarter we’ve been working on many improvements that will make your life easier when catching those sneaky bugs, and expand Bugfender’s capabilities with some of the most requested features:
- 💻 Improved 1.0 version of the web SDK with automated logging of UI Events and Browser events.
- 🧑💻 API documentation is now available together with an OpenAPI specification file that can be used to bootstrap your API client.
- 🕵️♂️ More search results: Bugfender is now more intelligent when indexing logs with JSON documents, class names, and camel-case strings, allowing you to find certain words more easily.
- ↔️ Log search/filter switch: when searching for some log text in the log viewer you can now switch between seeing all the logs or only the matching logs.
- 🔐 Fine-grained access control: we have added the ability to invite users to individual applications so that you can add, for example, your clients to their application, or manage different development teams in a larger company. (Pro plans and better only)
- 🆕 Bugfender On-Premise 2020.2 launched with all the recent updates included in the SaaS version.
We hope you find all these updates useful!
Infrastructure Improvements (Update 2020)
In this post, we’ll be highlighting some of the recent improvements we’ve made to Bugfender’s infrastructure. We’ve written it to ensure total transparency for our readers and (we hope) inspire other companies to make their own internal improvements.
So, if you are already reusing your code across several different projects, why not go the extra mile and convert it into a library that allows you to optimize this code-sharing? Creating a library will allow you to build different versions, keep track of the bugs that you fix and know exactly which version is using each project.
How to Create an npm Package Ready to Distribute From Scratch