-
-
Notifications
You must be signed in to change notification settings - Fork 230
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
resolved code formatting issue #371 #385
Conversation
pages/draft/2020-12/release-notes.md
Outdated
@@ -196,7 +200,7 @@ Here's how you would covert a schema using `$recursiveRef` to use `$dynamicRef`. | |||
} | |||
} | |||
} | |||
// strict-tree schema, guards against misspelled properties | |||
// strict-tree schema, guards against misspelled properties |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like there's still an issue with syntax highlighting. Probably is this comment.
Can you change the language specifier to jsonc
to see if that fixes the issue?
Sure @gregsdennis I'll try that too. |
Hi @gregsdennis I have tried some changes and now the UI looks like this |
pages/draft/2020-12/release-notes.md
Outdated
```json | ||
// tree schema, extensible | ||
<<<<<<< HEAD |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like there's an incomplete merge in here.
pages/draft/2020-12/release-notes.md
Outdated
<td> | ||
|
||
```json | ||
{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like the indention is being rendered. Can you pull this back to the start of the line, please?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
sure @gregsdennis i'll make the changes asap
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you check now @gregsdennis
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you push the changes? I don't see a difference in the code. Also, could you provide a screenshot? I can't run the site locally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
but at my end its showing the changes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see the indention changes I asked for. This is what's confusing.
Please move the JSON all the way to the left, ignoring the HTML indentation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now fine @gregsdennis ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @gregsdennis I changed the format to jsonc and now the output looks like this kindly check |
Now fine @gregsdennis ? |
The code looks good, but it still doesn't render right. The code has the correct indentation, but the render shows none. |
So what should I do now? |
Maybe this is related with the problems here: There are 2 config attributes in the code editor I needed to change to avoid extra width of the containing page for some scenarios for small devices, but the solution was suboptimal. I think this is related. Below the commit I did: related (maybe): react-syntax-highlighter/react-syntax-highlighter#376 |
Is this related to issue #393? |
The problem is with indentation right? Those 2 parameters affects exactly that. First play with them, later well need to check how to make sure the component's behavior is correct in other pages, specifically in small devices. |
Okay @benjagm I'll try that too. |
@Adity20 did you tested the component indentation disabling the attributes wrapLines and wrapLongLines? I think that can fix it. |
Yes I am testing out all the changes as you mentioned @benjagm will be done by tomorrow. |
I tried disabling these two attributes and tried some other changes too but that's creating an overflow in the page as the code is taking more space now to be in the same line. |
Can we have each section scroll horizontally? Would it be weird to have that here but not in other places? Alternatively, what if we made it look like a git diff, where you do a red |
I'd suggest fix everything but the indentation issue here and create an different issue to configure the code component to have its own horizontal scroll bar se fix this across the entire site. |
I'm happy with that |
So I should try horizontal scrollbar once or keep trying some other changes? |
@Adity20 I think si better to do it in a separate issue. Let suggest this:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great job @Adity20 !!!
Yeah that works for me @benjagm. I can start working on the that one then. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything except the indentation seems to be resolved. I'm happy address that elsewhere.
GitHub Issue: #371
Summary: This pull request is being made proactively to fix a particular problem which is code formatting for the issue #371.
Resolves #371
the UI looks like this now and if any other changes are required kindly let me @benjagm.
@benjagm kindly review my PR