Allow search by player name (hit remote API) and resolve to account_ids.

This can utilize the peers data for a player.

Continuation of odota/core#1119

be293d9#diff-d8b11c6bdcff4ca8523d8c80c06f2cf0R9

Currently the index.html references an external dependency:

    <link href="https://fonts.googleapis.com/icon?family=Material+Icons" rel="stylesheet">

This should be bundled in with webpack so that the site functions if Google changes the route or stops hosting the icons.

more descriptive name

example: put 10k matches limit filter on overview. Then swap to heroes tab. then go back to overview. Your filter will be gone because the page makes a request for the regular data amount which overrides the data. This causes a bug with pagination where you are stuck on a page which no longer exists, but the pagination controls don't render since that page is empty.

Footer has changed since we originally ported it.

Should API be a footer item or a main nav item?

Since we may be merging tabs, etc. we should define these lists of tab elements directly instead of pulling from constants.

skill = skill prop. Number->string mappings are in constants.js.
parse state = version prop. If truthy (not null and >0), match is parsed.

Also the base path should be /index, not /overview

New field in GetMatchDetails - "match_outcome". If dire won "match_outcome": 3, if radiant "match_outcome": 2. No more "radiant_win".
Check this out:

• https://yasp.co/matches/2452904337
• 
  
• https://yasp.co/matches/2452896443
• 
  
• https://yasp.co/matches/2452895531
• 
  
• https://yasp.co/matches/2452912581
• 
  

Yes, I was right. Аttached screenshots from the dota.

not quite sure why.

in last played column

Currently the table cells rendering with "subtext" class don't check for the field's existence.

• navbar runs off the screen instead of stacking
• home opening text runs offscreen
• player header elements overflow vertically
• TabBar navigation squishes together horizontally instead of wrapping
• overview match/hero tables are squished together (they should stack if the viewport is too narrow? bootstrap handles this automatically)
• home three features section should stack instead of compressing into 1/3 width
• Tables are way too wide in mobile scroll view.

@bguzryanto

I think the search page should update the URL in the address bar when a search is performed. Any query string produced by the user should be reflected in the address bar to allow URL sharing.

Bootstrap allows:
text-muted
text-danger
text-warning
text-success
text-primary

We should add similar global text color classes.

They should only show up for player pages (and a separate set for match pages).

Currently, if the user loads the home page and then tries to click a routing tab, it will lead to:

https://ui.yasp.co/players/undefined/overview

Currently we just skip the ability upgrades if the data is missing. With the SPA, we can have the client request ability upgrades separately from the server if they are missing (not already in the match object).

For now, the redirect will take the user back to the API host (which is current site).

Move column to leftmost after hero column. Replace "last match" with "last played"

The picture doesn't load initially (I'm guessing this is because the image path isn't in the store yet).

I think it's simplest just to have it say "profile" all the time (current behavior)

Continuation of odota/core#889

MVP:

• architecture @mike-robertson
• build search page @bguzryanto
• build request page @howardchung (WIP)
• build heroes pages (rankings/benchmarks) @marvizm, @bguzryanto (WIP)
• build distributions page @gu3st, @howardchung (WIP)
• build match pages @howardchung (WIP)
• build player pages @mike-robertson (WIP)
• player page filtering @mike-robertson (WIP)
• build home page @albertcui
• tooltips
• make usable on mobile

Telemetry/Sponsorship:

• make google analytics work @howardchung
• adsense @albertcui (dropping adsense)
• move donation code to own app @albertcui
• dotacoach @kennsippell
• jist @albertcui
• pvgna @albertcui
• becomethegamer @albertcui

Validation:

• test login @howardchung

Bonus:

• mmstats @albertcui
• status page
• banner (dismissable)
• page titles

People:
@howardchung
@albertcui
@mike-robertson
@gu3st
@stevenla
@Iparke
@bguzryanto
@Shenlok
@kkotwal94
@masad-frost
@bmulcahy
@Marvizm

Please indicate what you'd like to work on and coordinate with others working on the same area to avoid too many merge conflicts :)

The skill build layout currently looks terrible in my opinion.

When none of the heroes reach higher levels, the numbers are all clumped out without any spacing. Example

Secondly, the scroll bar is annoying. The user should be able to see all the levels at a glance. The issue is that the buildings minimap is taking quite a lot of space. It should be moved either above or below this data, like on dotabuff

found by @albertcui

https://beta.yasp.co/matches/2534821878

currently implemented for percent columns. Allow setting a property on any column to display bars relative to the maximum value of that column in the given table.

dependencies and devDependencies are 2 different things and they need to be separated. devDependencies are things that are required for dev/build process (webpack, webpack loaders etc.). dependencies are things which the application requires to run (react, react-dom, etc.).

• also is it possible to make the dropdowns appear without having to type anything
• also URL state needs to be updated when a filter is applied
• also text field should clear after a chip is selected
• constrain selections to max 1 element (on most fields)
• update w/l when a filter is applied
• also appears to be a bug where the ? doesn't show up in the URL sometimes

• We should be able to write "patch notes" in markdown or similar, and check them in as files.
• The UI should show these notes in a modal or similar
• The user should be able to dismiss the modal and it should not show up again (store in localStorage?)
• The message should not show up if it's too old (TTL)

• set ROOT_URL=api.opendota.com on backend (return point for steam openid)
• set UI_HOST=www.opendota.com on backend (redirect users to UI after login)
• set COOKIE_DOMAIN=.opendota.com on backend (cross-subdomain cookie)
• set API_HOST https://api.opendota.com on UI
• set CNAME www.opendota.com on UI
• set DNS to point opendota.com to odota.github.io
• enable redirect of beta to www

Users will need to login again since the domain has changed.

To test, go to peers on your profile. Then go to one of your peers pages by clicking the link. This won't update the tabbar's 'active' tab. I'm working on a pr to fix this.

the win/loss column in the player matches table is wrong

Looks like https://www.cookiechoices.org/ has code that can help with this.

Another person popped in last night and suggested the ability for an option to permanently enable ads.

I think it'd be a good thing.

Allow pagination on player/matches page to get more pages of matches.

Use "profile" instead of image, since image is not available unless the player profile has been loaded.

• go through the SPA and move any strings into language files
• figure out routing/persistence of language settings
• figure out how to load/update valve data in multiple languages
• have volunteer translators translate strings

Can swap with PiePercent, depending on which users like better

Currently, the user has to click the triple-bar icon in order to close the drawer.

Allow us to explicitly control order to prioritize important entries.

Currently on the first and last page, the arrow for the end won't render at all. This causes the entire page list to shift, which can confuse the user.

Noticeable when swapping tabs (e.g. heroes to peers). Perhaps there's something we can do to remedy this?

We should put the hash in the generated bundle name and inject the name to prevent GitHub pages from caching the bundle when we update.

var Path = require("path");
var FileSystem = require("fs");

var webpackConfig = {
    ...
    plugins: [
        ...
        function() {
            this.plugin("done", function(statsData) {
                var stats = statsData.toJson();

                if (!stats.errors.length) {
                    var htmlFileName = "index.html";
                    var html = FileSystem.readFileSync(Path.join(__dirname, htmlFileName), "utf8");

                    var htmlOutput = html.replace(
                        /<script\s+src=(["'])(.+?)bundle\.js\1/i,
                        "<script src=$1$2" + stats.assetsByChunkName.main[0] + "$1");

                    FileSystem.writeFileSync(
                        Path.join(__dirname, "%your build path%", htmlFileName),
                        htmlOutput);
                }
            });
        }
    ]
};

Apparently material-ui has them implemented, but not documented:
mui/material-ui#2230 (comment)

I don't know if they support direct HTML content, which we need since the data we have has raw HTML in it.

• items
• abilities
• table headers