Marzee’s Post

There has been a notable increase in data visualization projects at Marzee, and we are having a blast working on these projects. I wrote an article with a few of the benefits we see in using #reactjs for #datavisualization interfaces 🤘

If you are looking to build rich and robust data visualization apps, check out these essentials Allison Horst, PhD #DataVisualization #DataFam #DataAnalysis

So, an R data scientist walks into a JavaScript bar... I wrote this short primer with data scientists (like me!) in mind, with the aim of demystifying some unheralded essentials of building data apps with Framework. These are things that'll be familiar to JavaScript developers, but perhaps new to data teams & analysts working primarily in Python, R, SQL, etc. Also got an Inigo Montoya quote through review 🗡 Check it out!

Often, when building a GraphQL API, you want to model the API around a “viewer”. The viewer is the user who is currently authenticated and making the request to the API. This approach is called the “Viewer Pattern” and used by many popular GraphQL APIs, such as Facebook/Meta, GitHub, and others. Are you looking for an Open Source Graph Manager? Cosmo is the most complete solution including Schema Registry, Router, Studio, Metrics, Analytics, Distributed Tracing, Breaking Change detection and more. We’ve recently had a Schema Design workshop with one of our clients and discussed how the Viewer Pattern could be leveraged in a federated GraphQL API. In this article, I want to share the insights from this workshop and explain the benefits of implementing the Viewer Pattern in a federated Graph. What is the Viewer Pattern? The Viewer Pattern usually adds a viewer, me, or user field to the root of the GraphQL schema. This field represents the currently authenticated user and can be used to fetch data that is specific to the user, such as their profile, settings, but also data that is related to the user, such as their posts, comments, or other resources. Let’s take a look at an example schema that uses the Viewer Pattern: type Query { viewer: User! user(id: ID!): User @requiresClaim(role: "admin") } type User { id: ID! name: String! email: String! posts: [Post!]! comments: [Comment!]! } type Post { id: ID! title: String! content: String! } type Comment { id: ID! content: String! } Enter fullscreen mode Exit fullscreen mode In this example, the currently logged-in user can fetch their own profile, id, name, email, and all the posts and comments they have created. If you’re thinking in the context of a social media platform, it makes sense to model the API around the user, as we’ve always got an authenticated user and we usually want to fetch data that is related to them. At the same time, we also have a user field that can be used to fetch data about other users, but it requires the user to have the admin role. Modeling our API like this makes it easy to define access control rules and to fetch data that is specific to the current user. Let’s say we’d like to fetch the currently logged-in user’s profile, posts, and comments, this is how the query would look like: query { viewer { id name email posts { id title content } comments { id content } } } Enter fullscreen mode Exit fullscreen mode In contrast, if we didn’t use the Viewer Pattern, we would have to pass the user’s ID as an argument to every field that fetches data related to the user, like their profile, posts, comments, and so on. In this case, the GraphQL Schema would look like this: type Query { user(id: ID!): User posts(userId: ID!): [Post!]! comments(userId: ID!): [Comment!]! } type User { id:

Expressive, interactive data visualizations are the heroes of Observable Framework data apps. But behind the scenes are supporting software, tools, and architecture (like Node.js, npm, static site architecture, and data loaders) that play a key role in app performance and workflow flexibility. In our new blog post we demystify some unheralded essentials of building with Framework, so that data teams and analysts can more confidently jump into building best-in-class data apps:

💜 Developers love GoodData! Why? Because GoodData provides a wide range of developer tools that help developers in creating their analytics applications. One such tool is the integration of GoodData.UI with many different front-end frameworks. This framework-agnostic BI means that whatever framework you use, you’ll be able to customize GoodData easily to your needs with your existing practices. #dataanalytics #datavisualization #businessintelligence #BI #frontend

A Guide to ReactJS with D3 Integration: Harnessing the Power of Data Visualization https://lnkd.in/e2PEWkRA #reactjs #d3integration #datavisulization

How to Create Accessible Charts in React: A Guide to Inclusive Data Visualisation https://buff.ly/3Zls8mL #React #JavaScript #WebDev #WebDevelopment #DigitalAccessibility #Accessibility #A11y