-
Notifications
You must be signed in to change notification settings - Fork 49
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
Add support for rendering more logical classsynopsis markup #77
Conversation
…owing the old markup to render
'classname' => array( | ||
/* DEFAULT */ 'span', | ||
'ooclass' => array( | ||
/* DEFAULT */ 'format_suppressed_tags', | ||
'classsynopsisinfo' => 'format_classsynopsisinfo_ooclass_classname', | ||
), | ||
), |
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.
For reference, this is useless, as it duplicated the same information from the generic XHTML format.
Think this is looking pretty good from testing on my end. Only "issue" is that (php/doc-en#2563) is missing my previous changes for DS interfaces. So it reverts some items back to abstract modifiers I had removed from affected DS interface methods. Maybe not a big deal tho since rebase should fix that and I'll need to make adjustments so those work with this PR. |
Issue is because I guard the legacy renderer from the use of the |
@mallardduck merged this so feel free to fix the DS markup again. :) |
@Girgias - does gen_stub need to still be updated and ran on things? If I follow correctly that should cover core PHP things but not extensions right? Currently I am hitting the assertion you put in here: It seems to be being caused by Traversable having the class attribute, but using the structure from my PRs method. So it needs to be updated to match the syntax you've sorted out for us. Howveer should I update those by hand too, or is that what gen_stub should cover? |
@kocsismate is covering gen_stub, so don't worry about that. No, you don't need to convert any classes that use the "old" rendering, the example changes I made for Traversable are just an example of the markup and I don't really indent on changing them as that is going to be a lot of churn for translation for the time being. I would "just" change the interfaces for the time being to the new markup. |
Also gen_stub can cover PECL extensions (as I did that for ibm_db2) but it needs stub files, which last time I checked DS did not have. |
Ok - so is it expected that I should see build errors currently then? I'm seeing:
When I add a try-catch with good old dump-die, I see it's from
|
AHHH right I had forgotten those got updated to use your rendering >_> yeah those need to be fixed... I suppose let's just wait for @kocsismate to finish updating gen_stub so that we can fix those interfaces too |
Following php/phd#77
Following php/phd#77
I Just rebased php/doc-en#2638 atop @kocsismate branch and it looks like the error still happens
Is there more work to do in #2611 or is there a way to make a branch from before this PR merged? |
Are you sure you have the latest commits from doc-base, doc-en, and phd? As I can render the docs without any issues. Commands used from my phd clone:
|
So I'm running from outside of the phd repo, but I am on This is also affecting another builder, who instead of highlighting was working around using a commit pin. I can confirm that if I CD into phd, and copy-paste your commands I still get this error. |
|
Can you change the: if (!$this->cchunk["classsynopsis"]["legacy"] === true) { var_dump($name); } This might give some info without needed to go through a debugger |
@Girgias is this still waiting on @kocsismate to update gen_stub and rerun that? It seems a lot like what I reported last week. |
It has been updated, and the interfaces have been updated. Just classes still use the "legacy" rendering for the most part, which is somewhat incompatible with the output as I want to let translation some time to catch up. |
@kocsismate has not yet been merged, but I have done a 3 way branch including master, kocsismate and the new code, as well as tested this on just kocsismate and master. It would really help me to know which sha's are being used for the instructions above and if it works in a clean-install, or if there are maybe files or instructions I'm not following. I Started this to troubleshoot if there was a nicer way to handle https://github.com/php/doc-en/pull/2638/files#diff-38801fa32c4bd7bd97aa3c87c138be36e126e0337b22aacf27ab57365357dc20R10 as I think being able to build from master, branch or tag (all of which I can clone shallow) would work. The linked PR is not my work, but only works (same error as I've shown here) if pinning to a specific commit sha. |
@Lewiscowles1986 - looks like the current build errors are coming from DS needing to be updated for the new format. I'll send the follow up PR to update those for @Girgias syntax improvements. |
Thanks all and sorry for creating such noise on a merged branch 👍 . I'd love to know what DS is? |
@Girgias - sent a PR: php/doc-en#2641 to fix the DS docs. Seems to fix builds!
@Lewiscowles1986 - just shorthand for Data Structures extension. https://www.php.net/manual/en/intro.ds.php |
ACK currently not in front of a computer but will do it ASAP |
Follow-up on php/phd#77
while allowing the old markup to render.
@mallardduck @heiglandreas
I'll push an example of some doc-en changes that would render this markup.
From my testing (which is not the most extensive) nothing is broken.