profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/mpodlasin/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

stoplightio/cra-template-elements 0

Elements Create React App Template

stoplightio/gatsby-starter-elements 0

Gatsby Starter for Stoplight Elements

stoplightio/gatsby-starter-elements-dev-portal 0

Gatsby Starter for Stoplight Elements Dev Portal

push eventstoplightio/elements

Mateusz Podlasin

commit sha 9e059d00c8db654ab852794c77e030aa339c6304

fix: copy mock server url (#1760) * fix: copy mock server url * fix: remove unnecessary flex

view details

push time in 16 days

delete branch stoplightio/elements

delete branch : fix/copy-mock-server-url

delete time in 16 days

PR merged stoplightio/elements

Reviewers
fix: copy mock server url

Addresses https://github.com/stoplightio/elements/issues/1746

Screenshot 2021-09-10 at 15 07 23

+5 -10

3 comments

1 changed file

mpodlasin

pr closed time in 16 days

push eventstoplightio/elements

Mateusz Podlasin

commit sha 0fff8dd1483eefb9463f4c1048e100431be1b732

fix: remove unnecessary flex

view details

push time in 16 days

PR opened stoplightio/elements

Reviewers
fix: copy mock server url

Addresses https://github.com/stoplightio/elements/issues/1746

Screenshot 2021-09-10 at 15 07 23

+4 -9

0 comment

1 changed file

pr created time in 16 days

create barnchstoplightio/elements

branch : fix/copy-mock-server-url

created branch time in 16 days

issue closedstoplightio/elements

Chore: use markdown component override provider for relative links

Summary

Follow-up to: #1598

@marcelltoth @mmiask quick note - markdown-viewer has this sort of markdown component override provider built in now (stoplightio/markdown-viewer#95). Could switch to using it rather than the custom one here in elements, and get a nice code reduction win here. The one built into markdown-viewer also has benefit that the custom components will be leveraged even when markdown viewer is rendered in downstream components (for example markdown rendered in json schema viewer descriptions, etc).

closed time in 16 days

mmiask

push eventstoplightio/elements

Mateusz Podlasin

commit sha 3ae91fe219ffa346709e4f9ac696ce5ffbf0508d

chore: swap custom markdown provider for official one (#1754) Co-authored-by: Nauman <mnaumanali94@gmail.com>

view details

push time in 16 days

delete branch stoplightio/elements

delete branch : chore/use-markdown-provider

delete time in 16 days

push eventstoplightio/elements

Michael Miaskowski

commit sha 64b9f874bdd40a751c8c0302c281c17da93bbf60

Feat/hide internal operations (#1739) * feat: hide internal nodes update types returned by getNodes throwing errors for specific statuses added Forbidden screen updated Search component * feat: support brancSlug in useGetNodes hook Co-authored-by: Nauman <mnaumanali94@gmail.com>

view details

Mateusz Podlasin

commit sha ec89f0a7457e8f77dea91cbf0a1fb40fc6a229ec

Merge remote-tracking branch 'origin/main' into chore/use-markdown-provider

view details

push time in 16 days

push eventstoplightio/elements

Noah

commit sha 2b7f277fe401c7cb4644a46e4bf5e1c1ea698025

chore(toc): add bold font weight to toc component, addresses #1714 (#1755)

view details

William Hilton

commit sha 22e580c0b96d93d3a792ec7f2db75a0448458d31

chore: release 7.3.1 (#1756)

view details

Mateusz Podlasin

commit sha bf9aa1341b0cad2f01173939c36ade304b879621

Merge remote-tracking branch 'origin/main' into chore/use-markdown-provider

view details

push time in 16 days

PR opened stoplightio/studio

Modified docs/Documentation/03a-stoplight-flavored-markdown.md

Closes https://github.com/stoplightio/platform-internal/issues/7659

+85 -0

0 comment

1 changed file

pr created time in 16 days

push eventstoplightio/studio

Mateusz Podlasin

commit sha d166916bcc758879c0cf54b2e99f577faa41227e

Modified docs/Documentation/03a-stoplight-flavored-markdown.md

view details

push time in 16 days

PullRequestReviewEvent

Pull request review commentstoplightio/elements

feat (dev-portal): add search component

 import { NodeSearchResult } from '../types'; import { appVersion } from '../version';  export const getNodes = async ({-  workspaceId,   projectIds,+  workspaceId,   search,   platformUrl = 'https://stoplight.io',   platformAuthToken, }: {-  workspaceId: string;+  projectIds: string[];+  workspaceId?: string;   search?: string;-  projectIds?: string[];   platformUrl?: string;   platformAuthToken?: string; }): Promise<NodeSearchResult[]> => {   const queryParams = [];+  let fetchedWorkspaceId = workspaceId || ''; -  if (projectIds && projectIds.length) {-    queryParams.push(...projectIds.map((projectId, index) => `project_ids[${index}]=${projectId}`));+  if (!workspaceId) {+    const response = await fetch(`${platformUrl}/api/v1/projects/${projectIds[0]}`, {

Hmm, I am on the fence here.

On one hand it will likely work quite well, and it is a fast fix.

On the other, the cleaner solution would be to actually update elements-service, to not require workspaceId when searching nodes... 🤔

@wmhilton would appreciate your opinion here.

paulatulis

comment created time in 17 days

create barnchstoplightio/elements

branch : chore/use-markdown-provider

created branch time in 17 days

Pull request review commentstoplightio/elements

feat (dev-portal): add search component

 const PlatformProvider: React.FC<DevPortalProviderProps> = ({   platformAuthToken,   children, }) => {-  return <PlatformContext.Provider value={{ platformUrl, platformAuthToken }}>{children}</PlatformContext.Provider>;+  return (+    <PlatformContext.Provider value={{ platformUrl, platformAuthToken }}>+      <MosaicProvider>{children}</MosaicProvider>

I think this is 💯 proper approach. My only worry would be conflicts in platform.

In platform MosaicProvider and DevPortalProvider are used in separation, which is probably ok, because mosaic is used explicitly there (or at least will be).

So what happens when there are two MosaicProviders in the code? Does it crash? Cause bugs? Or is it safe? 🤔 Those questions would have to be answered before we can make that change.

paulatulis

comment created time in 18 days

PullRequestReviewEvent

Pull request review commentstoplightio/elements

feat (dev-portal): add search component

+import type { NodeSearchResult } from '@stoplight/elements-dev-portal';+import { Search as ElementsSearch, useGetNodes } from '@stoplight/elements-dev-portal';+import * as React from 'react';++export type SearchType = {+  projectIds: string[];+  workspaceId: string;+};+export const Search = ({ projectIds, workspaceId }: SearchType) => {+  const [search, setSearch] = React.useState('');+  const [open, setOpen] = React.useState(false);+  const { data } = useGetNodes({+    search,+    projectIds,+    workspaceId,+  });++  const handleClose = () => {+    setOpen(false);+    setSearch('');+  };++  const handleClick = (data: NodeSearchResult) => {+    console.log('clicked', data);

It wouldn't be that much more work to actually make it send you to a proper article url.

paulatulis

comment created time in 18 days

PullRequestReviewEvent

pull request commentstoplightio/elements

feat (dev-portal): add search component

Screenshot 2021-09-08 at 12 48 01

I've made it work. It only needed a MosaicProvider, because modals in Mosaic require it to work.

This however should be changed and MosaicProvider should be put in DevPortalProvider so that user's don't have to know anything about mosaic.

After this, I imagine everything should work. The only requirement for Search to work should be DevPortalProvider, nothing else. Sorry if this wasn't clear.

Screenshot 2021-09-08 at 12 50 05

paulatulis

comment created time in 18 days

push eventstoplightio/elements

Mateusz Podlasin

commit sha 827a12aa062656a474e1998fe9f0e7dfd20f67fe

fix: add mosaic provider

view details

push time in 18 days

issue closedstoplightio/elements

Try It: Add dropdown to select response body format (pretty or raw)

Design: https://www.figma.com/proto/IkNc59AU2JN5Kc1qbd2AiB/Elements?node-id=684%3A8256&viewport=-257%2C522%2C0.43354687094688416&scaling=min-zoom

As a docs consumer, I can switch between Preview and Raw response body formats, so I can view how the response data looks when rendered vs the raw response. See the dropdown selector on the right side of the "response" panel in the linked design.

If the dropdown would only have one option (if we can't show pretty for type of response for example), then don't show the dropdown at all.

<p></p>

  • Preview - Presenting the thing to a human
  • Raw - The actual response so it can be copied as is and put elsewhere.

Images

  • Mime Types
    • image/jpeg
    • image/gif
    • image/png
    • image/svg
    • image/* (bonus, but only if we can just throw it at the browser and see if it can display it)
  • Modes:
    • Preview - Render the image

JSON response

  • Mime Types
    • text/json
    • application/json
  • Modes:
    • Preview - "Pretty" version of JSON expanded onto multiple lines
    • Raw - Whatever comes back from fetch.

XML response

  • Mime Types
    • text/xml
    • application/xml
    • text/html
    • application/html
  • Modes:
    • Preview - "Pretty" version of XML expanded onto multiple lines
    • Raw - Whatever comes back from fetch.

Text response

  • Mime Types
    • text/plain
    • text/csv
    • text/*
  • Modes:
    • Raw - Whatever comes back from fetch.

Show a warning that we do not support these following responses, and do not offer either Preview or Raw.

  • audio/*
  • font/*
  • example/*
  • message/*
  • model/*
  • multipart/*
  • video/*

As with any Mime Type work, remember that application/foo+xml and application/xml; chartset=utf-8 should triggerapplication/xml. "Content Negotiation" tools can help with this, but basic string matching will always fail.

closed time in 18 days

marbemac

issue closedstoplightio/elements

Allow server URLs to be copied

There's no easy way to copy the Server URLs in elements.

Let's add an option for users to copy Server/Mock server URLs in the API overview which shows up on hover.

Also fix the HTML in this one to allow highlighting just the URL.

closed time in 18 days

mnaumanali94

issue closedstoplightio/elements

Incredibly long regex patterns need to be forcibly word wrapped

Describe the bug

Very very long validation properties like super-huge regex patterns are breaking display.

image

To Reproduce

https://learning.stoplight.io/docs/robotfactory/ZG9jOjYzMzI0-welcome#data-models

Expected behavior

Break the line to the next line for match regex, and any other validations.

closed time in 18 days

philsturgeon

issue openedstoplightio/elements

Copying server URL doesn't work for mock URL

We implemented copying server URL in API Overview section, but forgot to do the same for mock URL.

Screenshot 2021-09-06 at 11.33.19.png

created time in 20 days

push eventstoplightio/json-schema-viewer

Mateusz Podlasin

commit sha 39ad9e6f0e8bea6380a5ec79c9889037e6ccf0cc

fix: long validations (#166) * fix: long validations * fix: linter errors * fix: snapshot tests

view details

push time in 23 days