Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The content of IgxLabelDirective, IgxPrefixDirective and IgxSuffixDirective API doc pages is not properly displayed #3507

Closed
mtsvyatkova opened this issue Jan 2, 2019 · 3 comments
Assignees
Labels
🐛 bug Any issue that describes a bug 🆕 status: new

Comments

@mtsvyatkova
Copy link
Contributor

Description

The content of the following API doc pages is not properly displayed:

Steps to reproduce

  1. Open any of the above links
  2. Observe the loaded page.

Result

The content of the page is misaligned.

Expected result

The content of the page should be properly aligned.

Attachments

misalignedcontent

@mtsvyatkova mtsvyatkova added the 🐛 bug Any issue that describes a bug label Jan 2, 2019
@Aleksandyr Aleksandyr added the 🛠️ status: in-development Issues and PRs with active development on them label Jan 3, 2019
@Aleksandyr
Copy link
Contributor

@mtsvyatkova I wasn't able to reproduce the problem locally.
I have determined that all those files are commented as hidden which means that they shouldn't be able to be accessed. I have generated those documents locally and it worked as expected. Those files haven;t existed into that static generated site.

So my recommendation is to wait for the next triggered build and test that again. If it is reproducible again then we can try to investigate the problem deeper.

@Aleksandyr Aleksandyr added 🆕 status: new and removed 🛠️ status: in-development Issues and PRs with active development on them labels Jan 3, 2019
@Aleksandyr
Copy link
Contributor

Aleksandyr commented Jan 14, 2019

@mtsvyatkova @VMihalkov Has found the problem. It seems that when we trigger a new build it doesn't remove the previous content of the folder which is located at the build machines. Respectively if we hide something from the source code through the comments and than we trigger a new build the files which matches into that folder are replaced and the one that are hidden remains their and the problem appears.

The solution that @VMihalkov suggested is to create a shell string which at build time would clear that content and update it with the latest one.

So I'm leaving this issue open till the problem is resolved by ES team.

@Aleksandyr
Copy link
Contributor

Aleksandyr commented Jan 15, 2019

This PR should fix the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Any issue that describes a bug 🆕 status: new
Projects
None yet
Development

No branches or pull requests

2 participants