Skip to content

Conversation

@robpaveza
Copy link
Contributor

Network Console is an experimental UI for creating synthetic HTTP requests from DevTools. It is designed for web API developers and consumers, and is intended to be compatible with similar tools.

robpaveza added 6 commits June 2, 2020 14:18
Network Console is an experimental UI for creating synthetic HTTP
requests from DevTools. It is designed for web API developers
and consumers, and is intended to be compatible with similar tools.
In a move to migrate this to a single-file distribution, a necessary
component was to add CSP to this application. We've now identified
all the locations from which we load web-based sources. A future
version may move all of the dependencies directly into the
application.

Also removed a now-unused build script.
Copy link
Contributor

@joselea joselea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are many files so it will take me a while. Initial set of comments

Copy link
Member

@xirzec xirzec left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Left some thoughts, overall the project seems reasonable and well organized. Mostly nits and minor polish stuff.

Cool tool, happy to see React doing some work for you. Curious how good/bad your devloop was.


it('renders without crashing', () => {
const div = document.createElement('div');
ReactDOM.render(<App />, div);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe should be rendering this inside a Strict tag for extra checks?

);
}

const AUTH_SCHEME_NAME_MAP = new Map<NetworkConsoleAuthorizationScheme, string>([
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe these maps shouldn't live in the ux component?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why? They present UX strings (or the earlier map associates a value to a UX component index).

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Well presumably you'd maybe want to localize them somewhere else and I could see multiple components wanting to use the strings in the future. Maybe that's premature, it just feels weird to have only this component ever know about how these values translate to something readable.

Primarily, these are:
 - Build script comments describing what is done
 - React style and nits
Copy link
Contributor

@joselea joselea left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a very long list of files, understandable since its the initial port of files. I couldn't find anything wrong that stands up other that what we discussed in the comments. I'm approving with the understanding that this project will continue to be develop and that next PRs will be smaller.

Copy link

@bgoddar bgoddar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a few nits here and there. Looks like a couple of places in your actions and reducers had some random empty lines added that don't seem intentional.

Didn't spend much time reviewing the UI sections either, let me know if you want me to go back, but based on the last local test I did I don't think I would find much that isn't already mentioned

robpaveza added 10 commits June 4, 2020 12:41
 - Changed the title editor to be editable on click (always a text box)
 instead of via a button
 - Removed the splitter button (Send and Download) and moved Download
 functionality into the response viewer
 - Moved Computed URL and response stats into Status Bar views in
 the request and response sides
 - Split off the address bar components so they don't touch, and restored
 their rounded corners
 - Matched FAST styling for the editor grids - removed vertical
 gridlines
 - Removed color for response status
 - Vertical splitter resize bar - switched to gray and removed the
 % difference overlay
- "Create new request" does not create a tab for it
- Verb picker should not be free-form

Dark theme:
 - Links should be consistently styled
 - "These parameters may contain sensitive information" in authorization warning is white on yellow. Violates CC requirements.
Also corrected a bug in which HTML previews wouldn't be displayed
because they were blocked by CSP or the HTML content was too long.
@robpaveza robpaveza merged commit ad31640 into master Jun 10, 2020
@robpaveza robpaveza deleted the initial-checkin branch June 10, 2020 20:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants