Sites that sell.
Applications that solve.
Drupal, solved.
We're dedicated to helping solve digital solutions that matter to you.
Getting your site to effectively sell. Increasing your ROI. Improving your brand's digital experience. Solving your customer's needs.
If you're a Project Owner, Marketer, Technology Manager, or Business Owner with a need to make your digital work for you, we're here to help.
Investing the time to learn about the client's business and understand the project's goals is essential to creating a truly custom development strategy.
We'll design a purposeful web experience for your customers, based on objective information garnered during the Discovery and Strategy phases.
The effort spent on discovery and planning comes to life during development. We love implementing purposefully planned features and functionality in code.
We are here to help. Thinkbean remains a partner after the initial build or project to help support all efforts.
Emphasizing "Drupal experts", our team delivers the highest quality work, done right the first time. Our broad experience and profound knowledge of Drupal set us apart from the pack.
Thinkbean believes in creating applications with purpose. We learn about the organization's and users' goals before crafting a well-thought out, objective strategy for execution.
Don't just take our word for it. Read some of our most interesting case studies to uncover our true value.
When developing an API which has users with different roles accessing the data, there’s often properties which should only be accessible to privileged users.
I’ve written about how to restrict properties, by adding serialization groups to each property, but now we need to set the serialization context based on the current user.
Postman started out as an API development tool, but has developed more into, as they put it, an “API Development Environment”.
An over-simplified description is it allows you to create and save requests to test your API. You can then save your requests as a collection and share or publish them for others to use.
API Platform makes it easy to deliver all properties of an entity, but what about when you want to limit what properties are accessible to either GET or POST/PUT operations?
It’s surprisingly an easy bit of configuration.
What about dynamically limiting access to properties based on something like the user’s role?
This requires creating a service class, but it is still very approachable.
This article will cover:
