profile
viewpoint

stoplightio/desktop 77

The Stoplight desktop app + issues repository.

stoplightio/ui-kit 14

Foundational React components for the Stoplight ecosystem.

stoplightio/docs 11

Documentation for the Stoplight Next

stoplightio/formtron 11

JSON form builder for React.

stoplightio/http-spec 11

Utilities to normalize OpenAPI v2 and v3 objects for the Stoplight ecosystem.

stoplightio/yaml 8

Useful functions when working with YAML.

stoplightio/scripts 5

Scripts to aid in testing, releasing, and linting.

stoplightio/httpsnippet 3

HTTP Request snippet generator for many languages & libraries

stoplightio/storybook-config 3

Shared storybook config for UI-Kit based project.

stoplightio/gitlabhq 2

StopLight's customized fork of Gitlab

Pull request review commentstoplightio/platform-docs

Pam 220 scopes for oauth apps

+# Troubleshoot Git Connections++Use these troubleshooting steps to resolve errors related to your Git connections.++## Verify Integration Settings++1. Select **Settings** from the workspace home page, then navigate to the **Integrations** section.+2. Locate your Git integration (GitHub, GitLab, etc.), and verify that it is enabled.+3. Select the arrow to the right of the integration.+4. Verify that these settings match those in your Git provider:+   - Client ID and Client Secret+   - Host and API URL+   - Scopes and permission settings for your integration++See Stoplight requirements for each provider type:++- [Bitbucket Cloud](b.bitbucket-cloud.md)+- [Bitbucket Server](c.bitbucket-server.md)+- [GitHub Enterprise](d.github-enterprise.md)+- [GitLab](e.gitlab.md)++## Verify Firewall Settings+If you are connected behind a firewall, verify that Stoplight's IP addresses are added to your allowlist. ++The fixed IP address is: **35.226.194.249**.++## Reinstall Webhooks

Maybe it's worth mentioning that they can check the recent deliveries for webhooks in their VCS to get more info on if and why recent webhook deliveries have failed?

image

pamgoodrich

comment created time in 17 hours

Pull request review commentstoplightio/platform-docs

Pam 220 scopes for oauth apps

+# Troubleshoot Git Connections++Use these troubleshooting steps to resolve errors related to your Git connections.++## Verify Integration Settings++1. Select **Settings** from the workspace home page, then navigate to the **Integrations** section.+2. Locate your Git integration (GitHub, GitLab, etc.), and verify that it is enabled.+3. Select the arrow to the right of the integration.+4. Verify that these settings match those in your Git provider:+   - Client ID and Client Secret+   - Host and API URL+   - Scopes and permission settings for your integration++See Stoplight requirements for each provider type:++- [Bitbucket Cloud](b.bitbucket-cloud.md)+- [Bitbucket Server](c.bitbucket-server.md)+- [GitHub Enterprise](d.github-enterprise.md)+- [GitLab](e.gitlab.md)++## Verify Firewall Settings+If you are connected behind a firewall, verify that Stoplight's IP addresses are added to your allowlist. ++The fixed IP address is: **35.226.194.249**.++## Reinstall Webhooks++Webhooks are used to automatically sync data between Stoplight and your Git repository. Typically, you install webhooks when you create your Git project in Stoplight, but you can reinstall them if you have any issues.++1. Log in to your workspace, and edit the project you are troublshooting.+2. Select the **Project Settings** icon.+3. Select the **Automation** tab. (This tab is only visible for projects connected to a Git repository.)+4. Select **Install**.++## Reset Stoplight Access++If connection issues persist, revoke Stoplight authorization in your Git application, and then reauthorize.++## Remove Integration++Consider removing the integration from Stoplight, then confirming you can clone the Git repository to location outside of Stoplight. 

I think you should mention cloning with HTTP and not SSH. So maybe

then confirming you can clone the Git repository using the HTTP/HTTPS URL to a location outside of Stoplight.

That goes with the GitLab tid bit you added of ensuring that cloning with HTTP/HTTPS is enabled.

pamgoodrich

comment created time in 17 hours

Pull request review commentstoplightio/platform-docs

Pam 220 scopes for oauth apps

+# Troubleshoot Git Connections++Use these troubleshooting steps to resolve errors related to your Git connections.++## Verify Integration Settings++1. Select **Settings** from the workspace home page, then navigate to the **Integrations** section.+2. Locate your Git integration (GitHub, GitLab, etc.), and verify that it is enabled.+3. Select the arrow to the right of the integration.+4. Verify that these settings match those in your Git provider:+   - Client ID and Client Secret+   - Host and API URL+   - Scopes and permission settings for your integration++See Stoplight requirements for each provider type:++- [Bitbucket Cloud](b.bitbucket-cloud.md)+- [Bitbucket Server](c.bitbucket-server.md)+- [GitHub Enterprise](d.github-enterprise.md)+- [GitLab](e.gitlab.md)++## Verify Firewall Settings+If you are connected behind a firewall, verify that Stoplight's IP addresses are added to your allowlist. ++The fixed IP address is: **35.226.194.249**.

Take this or leave this... but should you link to the other page that already lists this? That way if that info ever changes you only have one spot to update?

pamgoodrich

comment created time in 17 hours

PullRequestReviewEvent
PullRequestReviewEvent

issue commentstoplightio/platform-docs

Document scopes for each OAuth App

  1. GitHub --> Enablers can look up the scopes that are set for our Production GitHub.com OAuth App
  2. BitBucket Server --> N/A, does not support OAuth
  3. BitBucket Cloud --> Enablers can look up the scopes that are set for our Production Bitbucket.org OAuth App
  4. Azure Devops Server -->N/A, does not support OAuth
  5. GitLab --> you already have it
pamgoodrich

comment created time in 15 days

Pull request review commentstoplightio/platform-docs

Pam 180 restrict guest access

 Workspace roles are predefined according to varying access needs. You can assign  Roles include:  -**Guests**: Restricted to view documentation for projects that they are granted explicit access to. Guests are typically users outside your company or organization, such as partners who require authenticated access to the documentation. +**Guests**: Restricted to viewing documentation for projects that they are granted explicit access to. Guests are typically users outside your company or organization, such as partners who require authenticated access to the documentation. 

Yeah that works for me! Also leaving it as-is works for me too haha.

pamgoodrich

comment created time in 2 months

PullRequestReviewEvent
PullRequestReviewEvent

Pull request review commentstoplightio/platform-docs

Pam 180 restrict guest access

 To update the project visibility or add users to a project, select the **Share**  ## Project Roles -Project roles determine the level of access for each project member. These roles include:+Project roles determine the level of access for each project member. To change a user's role for a project, open the **Share** dialog, locate the user, then change the role.   **Viewer**: Members with viewer access can view documentation and access mock servers for published and unpublished branches. Guests have restricted access and can only view documentation in published branches. (Guests are automatically given restricted access when they are invited to a project.)

should you add a callout for the Guest role here?

pamgoodrich

comment created time in 2 months

PullRequestReviewEvent

Pull request review commentstoplightio/platform-docs

Pam 180 restrict guest access

 Workspace roles are predefined according to varying access needs. You can assign  Roles include:  -**Guests**: Restricted to view documentation for projects that they are granted explicit access to. Guests are typically users outside your company or organization, such as partners who require authenticated access to the documentation. +**Guests**: Restricted to viewing documentation for projects that they are granted explicit access to. Guests are typically users outside your company or organization, such as partners who require authenticated access to the documentation. 

should you also mention that they can view documentation for public projects? Or is that a given since everyone, even anonymous can view public projects?

pamgoodrich

comment created time in 2 months

issue commentstoplightio/prism

Postman plus Prism Proxy causes errors

This was specifically removed as part of https://github.com/stoplightio/prism/pull/1319 so we'll have to take a look at why it was removed and what will happen if we add back the compress flag.

lornajane

comment created time in 2 months

issue closedstoplightio/elements

x-internal operations are still visible on documentation

User story.

As an API designer role person I want to mark certain operations as internally visible in order to hide those operations from public display on documentation

Is your feature request related to a problem?

Compatibility problem related to documentation consistency

Describe the solution you'd like

When I'm using stoplight as publishing platform is posible to me acomplish this using the extended property "x-internal", so it would nice that Webcomponent would to have the same behavior

closed time in 3 months

rolivares

issue commentstoplightio/elements

x-internal operations are still visible on documentation

Fix released in 7.3.8

rolivares

comment created time in 3 months

push eventstoplightio/elements

Chelsea Hohmann

commit sha c62c2674ab2723e674210c245b8920125e2e6082

chore: release 7.3.8 (#1833)

view details

push time in 3 months

delete branch stoplightio/elements

delete branch : chore/release-7.3.8

delete time in 3 months

PR merged stoplightio/elements

Reviewers
chore: release 7.3.8

releases fix for: https://github.com/stoplightio/elements/issues/1805.

PR that it releases is: https://github.com/stoplightio/elements/pull/1830

+1 -1

3 comments

1 changed file

chohmann

pr closed time in 3 months

PR opened stoplightio/elements

chore: release 7.3.8

releases fix for: https://github.com/stoplightio/elements/issues/1805.

PR that it releases is: https://github.com/stoplightio/elements/pull/1830

+1 -1

0 comment

1 changed file

pr created time in 3 months

create barnchstoplightio/elements

branch : chore/release-7.3.8

created branch time in 3 months

push eventstoplightio/elements

Chelsea Hohmann

commit sha 9a20992b31f31a0fbd9ffe89ba1165084d59c906

feat: don't render groups with no items (#1830)

view details

push time in 3 months

delete branch stoplightio/elements

delete branch : fix/1805-do-not-render-empty-groups

delete time in 3 months

PR merged stoplightio/elements

Reviewers
fix: don't render groups that have no items

Addresses #1805

If a group does not contain any items (possible if all the items are x-internal and hideInternal flag is true) do not render the group.

+410 -452

3 comments

3 changed files

chohmann

pr closed time in 3 months

push eventstoplightio/elements

Stoplighticus Roboticus

commit sha 1f1d82e53dd1c95db81d061ec8936f5b635098b8

chore: weekly lockfile maintenance (#1831) Co-authored-by: stoplight-bot <support@stoplight.io>

view details

chohmann

commit sha c03af21629ea2812fc7c8d8fe2b3b58e6bb81792

Merge branch 'main' into fix/1805-do-not-render-empty-groups # Conflicts: # yarn.lock

view details

push time in 3 months

issue commentstoplightio/elements

File Upload button not working properly. Some seconds after selecting some file to upload, Send Request form is being erased suddenly

as discussed on our call today @mpodlasin is going to take this issue over as it looks like it's related to some core infrastructure for elements. He's better equipped to make the call on what to do based on his investigation. Re-assigning ticket to him.

manuelfhp

comment created time in 3 months

create barnchstoplightio/elements

branch : fix/form-data-body-resetting

created branch time in 3 months

PullRequestReviewEvent

Pull request review commentstoplightio/elements

fix: don't render groups that have no items

 export const computeAPITree = (serviceNode: ServiceNode, config: ComputeAPITreeC     });      groups.forEach(group => {-      tree.push({-        title: group.title,-        items: group.items.flatMap(operationNode => {-          if (mergedConfig.hideInternal && operationNode.data.internal) {-            return [];-          }-          return {-            id: operationNode.uri,-            slug: operationNode.uri,-            title: operationNode.name,-            type: operationNode.type,-            meta: operationNode.data.method,-          };-        }),+      const items = group.items.flatMap(operationNode => {+        if (mergedConfig.hideInternal && operationNode.data.internal) {+          return [];

There is a notion of marking items in your specs (i.e operations, models, etc.) as "Internal". If something is marked as internal then only members of your workspace will be able to see those items. So this is basically filtering out those internal items if the hideInternal flag is set (which it will be if being viewed by someone unauthenticated or not a member of the workspace). At least that's my understanding. This is my first time in this code base 😄

As for returning an empty array, flatMap flattens one level. So that empty array gets flattened into the outer array and essentially adds no items to the array.

Also, GitHub diff is weird, but basically just pulled the existing items definition out of the object so that I could check the length before pushing it onto the tree. So I didn't add or change that logic at all.

chohmann

comment created time in 3 months

issue closedstoplightio/prism

Allow end user to configure global faker options

User story.

As a Prism user, I can configure global faker/json-schema-faker options.

Is your feature request related to a problem?

There are lots of useful global json schema faker options, but no way to configure them. We set hard coded defaults here - https://github.com/stoplightio/prism/blob/master/packages/http/src/mocker/generator/JSONSchema.ts#L11-L20.

Describe the solution you'd like

Open to suggestions, but the simplest and most consistent option that I can think of is to add support for a root level x-faker object prop in the openapi document to override/extend our defaults.

openapi: 3.0.0

x-faker:
  # pass through faker options (there is only one relevant one I think?)
  # https://github.com/marak/Faker.js/#localization
  locale: de

  # pass through json-schema-faker options to override defaults. in this case always generating one array item
  # https://github.com/json-schema-faker/json-schema-faker/tree/master/docs#available-options
  minItems: 1
  maxItems: 1

# ... rest of document

Additional context

Related issues: #1139 #1160 <br><br><i>(related to <a href='https://stoplight.zendesk.com/agent/tickets/5164'>Zendesk ticket #5164</a>)<br>gz#5164</i>

closed time in 3 months

marbemac

issue commentstoplightio/prism

Allow end user to configure global faker options

closed by https://github.com/stoplightio/prism/pull/1899.

marbemac

comment created time in 3 months

more