Closed richnsoos closed 9 years ago
This is most likely a CSS concern. We can't fix it in this repository, but I'd be happy to pass it on to our frontend team and see if there's anything they can do about it. Do you have a sample document I could show them?
Thanks @bkeepers. My document is on GH Enterprise so I won't be able to share it, but here's the markup for the table if that helps:
[width="100%", options="header"] |=== |Name + Location |Description |How is it used? |Sample Values
|User Status Message + Field name: + +EVT_DETL_KEY_TXT.userStatusMessage+ + Table name: + +EVT_DETL+ |Client-readable message generated and defined by the API Delivery Team that describes the exception (IT failure, partial success, look aside data, enactment of a business rule) that the API returns to the client. Maps to User Status Code. |Digital Operations uses the Event Type Code, User Status Code, User Status Message, and HTTP Status Code to determine the disposition of the event when creating customer experience and analytical reports. |"Our system experienced an error. Please try again later. For help right now, you can call us at 1-800-xxx-xxxx." + "Alternate flow for rewards information."
|SSOID + Field name: + +USER_ID+ + Table name: + +EVT_AUDTG+ |Unique identifier of the end user (customer). In the case of Mobile, the RSA Web Agent sets the SSOID. |Digital Operations and Data Analysts use the SSOID to tie together all the events generated by a particular customer to build a picture of the customer experience for analytical reports. |xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
|Client Correlation ID + Field name: + +EVT_DET_KEY_TXT.Client-Correlation-Id+ + Table name: + +EVT_DETL+ |An optional field that clients can provide to any API service to track traffic across different APIs. If this ID is provided, its value will be audited. Otherwise, it will be ignored. Clients who utilize this are responsible for generating the value, guaranteeing uniqueness, and providing it as a Header in every request sent to an API. |Digital Operations and Data Analysts use this data when creating customer experience and analytical reports. |111111-222222-333333 + String(60) |===
Thanks again for helping~
Thanks. Is this the same way you are seeing it rendered on GHE? https://gist.github.com/bkeepers/ef1725a143a1fd7d0b7e
No. The table does not appear to display the same in GH as it does in GHE. In GHE, there is no horizontal scroll bar displayed, whereas in GH there is a horizontal scroll bar. I've attached a screen shot of the way the original table is displayed in GHE. My goal is to give column width preference to the center two columns and force text wrapping where possible on text in the first and last columns.
Hi @bkeepers, I know this is a closed issue, but I was wondering if you had any ideas if I wanted to change the breaking behavior for text within an AsciiDoc table in GHE. It appears that GH and GHE are rendering same content differently, ie: GHE will break at a dash (as shown in my image for EVT_DET_KEY_TXT.Client-Correlation-Id) but GH does not break at the dash (as shown in the secret gist you created for same id). In any event, I want to force breaking to happen on dashes and periods. Any thoughts?
I have an asciidoc table in an *.adoc page in a GHE repo. I'd like to change the wrapping rules that apply to content within cells of an asciidoc table. It's obvious that wrapping on a "-" is allowed because it's happening, but I'd like to allow wrapping on "." as well. Is this behavior controlled via asciidoc markup or the github rendering engine? The column specifiers for the col attribute for an asciidoc table do not seem to be honored if text within the column is a long string without an special characters on which wrapping occurs.
Wrapping happens on this string at the first "-": EVT_DET_KEY_TXT.Client-Correlation-Id Displayed as: EVT_DET_KEY_TXT.Client- Correlation-Id
Wrapping does not happen on this string at the ".": EVT_DETL_KEY_TXT.userStatusMessage Displayed as: EVT_DETL_KEY_TXT.userStatusMessage
If this is not the best spot for this question, apologies!